Vulnerability in php5 (UBUNTU-CVE-2025-14179)

Summary

Vulnerability in php5 (UBUNTU-CVE-2025-14179). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 7.0.33-0ubuntu0.16.04.16+esm19 or later.

Original description

The description as published by the source.

In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the PDO Firebird driver improperly handles NUL bytes when preparing SQL queries. During token-by-token query construction, a string token containing a NUL byte is copied via strncat(), which stops at the NUL byte, dropping the closing quote and causing subsequent SQL tokens to be interpreted as part of the string. This allows SQL injection when attacker-controlled values are quoted via PDO::quote() and embedded in SQL statements.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2025-14179 has been found in php5.
Successful exploitation can lead to full system takeover.
What to do: upgrade php5 to 7.0.33-0ubuntu0.16.04.16+esm19 or later.
If unsure, ask your IT team or search "php5 UBUNTU-CVE-2025-14179" on the vendor's site.

UBUNTU-CVE-2025-14179 (php5)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.0.33-0ubuntu0.16.04.16+esm19 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in php5.

📍 Affected scope

Check the vendor advisory for the affected versions of php5.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 7.0.33-0ubuntu0.16.04.16+esm19.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'php5' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'php5' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で php5 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade php5 to 7.0.33-0ubuntu0.16.04.16+esm19
```
ステージング環境で 7.0.33-0ubuntu0.16.04.16+esm19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS php5

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:16.04:LTS php7.0

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.33-0ubuntu0.16.04.16+esm19"}]}]

Ubuntu:Pro:18.04:LTS php7.2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:20.04:LTS php7.4

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:22.04:LTS php8.1

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.1.2-1ubuntu2.24"}]}]

Ubuntu:24.04:LTS php8.3

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.3.6-0ubuntu0.24.04.9"}]}]

Ubuntu:25.10 php8.4

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.11-1ubuntu1.2"}]}]

Ubuntu:26.04:LTS php8.5

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.5.4-0ubuntu1.1"}]}]

References

advisory ubuntu.com
advisory ubuntu.com
report ubuntu.com
report cve.org
report github.com
report github.com