Summary
ibexa/post-install affected by Breach with Varnish VCL
Workarounds
Make sure HTTP compression is disabled for REST API requests and other communication that might contain secrets.
References
- Advisory: https://developers.ibexa.co/security-advisories/ibexa-sa-2024-006-vulnerabilities-in-content-name-pattern-commerce-shop-and-varnish-vhost-templates
- Release notes v3.3: https://doc.ibexa.co/en/latest/update_and_migration/from_3.3/update_from_3.3/#v3341
- Release notes v4.6: https://doc.ibexa.co/en/latest/update_and_migration/from_4.6/update_from_4.6/#v4614
- https://github.com/ezsystems/ezplatform-http-cache/security/advisories/GHSA-mgfg-7533-7jf6
- https://github.com/ibexa/http-cache/security/advisories/GHSA-fh7v-q458-7vmw
- https://www.breachattack.com/
Impact
This is not a vulnerability in the code per se, but included platform.sh Varnish VCL templates and Apache/Nginx vhost templates enable compression of API and JSON messages. This is a potential case of the BREACH vulnerability, which affects HTTP compression, where secrets can be extracted through carefully crafted requests. The fix disables compression in these templates. Please make sure to make the same change in your configuration files, see the release notes for specific instructions.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Frequently Asked Questions
- What is GHSA-4H8F-C635-25P7? GHSA-4H8F-C635-25P7 is a medium-severity security vulnerability in ibexa/post-install (composer), affecting versions >= 1.0.0, < 1.0.16. It is fixed in 1.0.16, 4.6.14.
- Which versions of ibexa/post-install are affected by GHSA-4H8F-C635-25P7? ibexa/post-install (composer) versions >= 1.0.0, < 1.0.16 is affected.
- Is there a fix for GHSA-4H8F-C635-25P7? Yes. GHSA-4H8F-C635-25P7 is fixed in 1.0.16, 4.6.14. Upgrade to this version or later.
- Is GHSA-4H8F-C635-25P7 exploitable, and should I be worried? Whether GHSA-4H8F-C635-25P7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-4H8F-C635-25P7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-4H8F-C635-25P7?
- Upgrade
ibexa/post-installto 1.0.16 or later - Upgrade
ibexa/post-installto 4.6.14 or later
- Upgrade