GHSA-qmqw-mpqp-mr54
GHSA-qmqw-mpqp-mr54 is a CWE-284 vulnerability in symfony/http-kernel. O3 Security confirms whether GHSA-qmqw-mpqp-mr54 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Symfony Incorrect Access Control
Real-World Exposure
symfony/http-kernel🐘symfony/http-kernel🐘symfony/http-kernel🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/http-kernelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
FragmentListener in the HttpKernel component in Symfony 2.3.19 through 2.3.28, 2.4.9 through 2.4.10, 2.5.4 through 2.5.11, and 2.6.0 through 2.6.7, when ESI or SSI support enabled, does not check if the _controller attribute is set, which allows remote attackers to bypass URL signing and security rules by including (1) no hash or (2) an invalid hash in a request to /_fragment.
This issue has been fixed in Symfony 2.3.29, 2.5.12, and 2.6.8. Note that no fixes are provided for Symfony 2.4 as it's not maintained anymore.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/http-kernel | ≥ 2.3.19&&< 2.3.29 | 2.3.29 |
| 🐘Packagist | symfony/http-kernel | ≥ 2.5.4&&< 2.5.12 | 2.5.12 |
| 🐘Packagist | symfony/http-kernel | ≥ 2.6.0&&< 2.6.8 | 2.6.8 |
| 🐘Packagist | symfony/symfony | ≥ 2.3.19&&< 2.3.29 | 2.3.29 |
| 🐘Packagist | symfony/symfony | ≥ 2.4.9 | No fix |
| 🐘Packagist | symfony/symfony | ≥ 2.5.4&&< 2.5.12 | 2.5.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/http-kernel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update symfony/http-kernel to 2.3.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qmqw-mpqp-mr54 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qmqw-mpqp-mr54 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qmqw-mpqp-mr54. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qmqw-mpqp-mr54 in your dependencies?
O3 detects GHSA-qmqw-mpqp-mr54 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.