Code Injection in phpfastcache/phpfastcache (CVE-2019-16774)
Summary
Code injection in phpfastcache/phpfastcache (CVE-2019-16774). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.0.13 or later.
Original description
The description as published by the source.
Impact
An possible object injection has been discovered in cookie driver prior 5.0.13 versions (of 5.x releases).
Patches
The issue has been addressed by enforcing JSON conversion when deserializing
Workarounds
If you can't fix it, use another driver such as "Files" (Filesystem)
References
Fixing release: https://github.com/PHPSocialNetwork/phpfastcache/releases/tag/5.0.13
For more information
If you have any questions or comments about this advisory:
- Open an issue in the issue tracker
- Email us at security@geolim4.com
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-2019-16774 has been found in phpfastcache/phpfastcache.
Risk of unauthorized operations or information disclosure.
What to do: upgrade phpfastcache/phpfastcache to 5.0.13 or later.
If unsure, ask your IT team or search "phpfastcache/phpfastcache CVE-2019-16774" on the vendor's site.
CVE-2019-16774 (phpfastcache/phpfastcache) — CWE-94
Attack vector: remote (network-reachable)
Patched: 5.0.13 — apply immediately
Workaround: If you can't fix it, use another driver such as "Files" (Filesystem)
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.
Arbitrary code execution (CWE-94) exists in phpfastcache/phpfastcache.
Check the vendor advisory for the affected versions of phpfastcache/phpfastcache.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.0.13.
Workaround: If you can't fix it, use another driver such as "Files" (Filesystem)
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phpfastcache/phpfastcache' . 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 'phpfastcache/phpfastcache' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phpfastcache/phpfastcacheを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you can't fix it, use another driver such as "Files" (Filesystem)パッチが適用されるまでの応急処置として、If you can't fix it, use another driver such as "Files" (Filesystem) を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade phpfastcache/phpfastcache to 5.0.13ステージング環境で 5.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com