How severe is GHSA-mgfg-7533-7jf6?

No CVSS score has been assigned to GHSA-mgfg-7533-7jf6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mgfg-7533-7jf6?

GHSA-mgfg-7533-7jf6 affects the following packages: ezsystems/ezplatform-http-cache (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mgfg-7533-7jf6?

Update ezsystems/ezplatform-http-cache to 2.3.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgfg-7533-7jf6 is resolved across your whole dependency graph.

How do I detect GHSA-mgfg-7533-7jf6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-http-cache, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mgfg-7533-7jf6 if there is no patch (or I can't update yet)?

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.

Is GHSA-mgfg-7533-7jf6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mgfg-7533-7jf6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-mgfg-7533-7jf6 published, and has it been updated?

GHSA-mgfg-7533-7jf6 was published on December 2, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

ezsystems/ezplatform-http-cache affected by Breach with Varnish VCLGHSA-mgfg-7533-7jf6

Fix: ezsystems/ezplatform-http-cache@ca8a5cf

GHSA-mgfg-7533-7jf6 is a security vulnerability in ezsystems/ezplatform-http-cache. A fix is available for ezsystems/ezplatform-http-cache — see the affected versions and patch details below.

Published

Dec 2, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ezsystems/ezplatform-http-cache

Real-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

Impact

This is not a vulnerability in the code per se, but included Varnish VCL 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. Please check your web server configuration as well.

Patches

See "Patched versions".
https://github.com/ezsystems/ezplatform-http-cache/commit/ca8a5cf69b2c14fbec90412aeeef5c755c51457b

Workarounds

Make sure HTTP compression is disabled for REST API requests and other communication that might contain secrets.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezplatform-http-cache`	all versions	2.3.16`composer require ezsystems/ezplatform-http-cache:^2.3.16`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-http-cache, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform-http-cache to 2.3.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgfg-7533-7jf6 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.

Frequently Asked Questions

### Impact This is not a vulnerability in the code per se, but included Varnish VCL 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. Please check your web server configuration as well. ### Patches - See "Patched versions". - https://github.com/ezsystems/ezplatform-http-ca

O3 Security · Impact-Aware SCA

Is GHSA-mgfg-7533-7jf6 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works