Vulnerability in php7.4 (DEBIAN-CVE-2021-21705)
Summary
Vulnerability in php7.4 (DEBIAN-CVE-2021-21705). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.4.21-1+deb11u1 or later.
Original description
The description as published by the source.
In PHP versions 7.3.x below 7.3.29, 7.4.x below 7.4.21 and 8.0.x below 8.0.8, when using URL validation functionality via filter_var() function with FILTER_VALIDATE_URL parameter, an URL with invalid password field can be accepted as valid. This can lead to the code incorrectly parsing the URL and potentially leading to other security implications - like contacting a wrong server or making a wrong access decision.
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 DEBIAN-CVE-2021-21705 has been found in php7.4.
Risk of unauthorized operations or information disclosure.
What to do: upgrade php7.4 to 7.4.21-1+deb11u1 or later.
If unsure, ask your IT team or search "php7.4 DEBIAN-CVE-2021-21705" on the vendor's site.
DEBIAN-CVE-2021-21705 (php7.4)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.4.21-1+deb11u1 — 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.
A vulnerability (unclassified) exists in php7.4.
Check the vendor advisory for the affected versions of php7.4.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 7.4.21-1+deb11u1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'php7.4' . 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
-
1Identify exposure identify
grep -r 'php7.4' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
php7.4を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade php7.4 to 7.4.21-1+deb11u1ステージング環境で 7.4.21-1+deb11u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org