Unsafe Deserialization in phpmussel/phpmussel (CVE-2020-4043)
Summary
Vulnerability in phpmussel/phpmussel (CVE-2020-4043). Data can be tampered with by attackers. Exploitable via check_archives. Mitigation: upgrade to 1.6.0 or later.
Original description
The description as published by the source.
Impact
What kind of vulnerability is it? Who is impacted?
Anyone using >= v1.0.0 < v1.6.0.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes. Upgrading to at least >= v1.6.0 (the earliest safe version) will resolve the problem. However, as multiple new major versions have been released since that version, upgrading to the latest available version is recommended, in order to protect against any potential future vulnerabilities, unknown at the time of writing this advisory.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Yes. In the package's configuration, disable archive checking by setting check_archives to false (thus avoiding execution of the affected parts of the codebase entirely).
References
Are there any links users can visit to find out more?
Yes. The vulnerability is documented at SECURITY.md and also at #167.
For more information
If you have any questions or comments about this advisory:
- Comment at the issue linked to this advisory, or..
- Contact the package author.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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 CVE-2020-4043 has been found in phpmussel/phpmussel.
Attackers can target a specific entry point like check_archives over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade phpmussel/phpmussel to 1.6.0 or later.
If unsure, ask your IT team or search "phpmussel/phpmussel CVE-2020-4043" on the vendor's site.
CVE-2020-4043 (phpmussel/phpmussel) — CWE-502
Attack vector: remote (network-reachable) / no user interaction
Attack surface: check_archives / false
Patched: 1.6.0 — 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.
Unsafe deserialization (CWE-502) exists in phpmussel/phpmussel. Attackers reach the vulnerable code path via check_archives.
Check the vendor advisory for the affected versions of phpmussel/phpmussel. Attack surface: check_archives / false.
Severity: ?. Data can be tampered with by attackers.
Update to 1.6.0.
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 'phpmussel/phpmussel' . 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 'phpmussel/phpmussel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phpmussel/phpmusselを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade phpmussel/phpmussel to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com