GHSA-cfc2-wjcm-c8fm
HIGHIncorrect Authorization with specially crafted requests
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/pomerium/pomerium🐹github.com/pomerium/pomeriumReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Envoy, which Pomerium is based on, contains two authorization related vulnerabilities:
- CVE-2021-32777: incorrectly transform a URL containing a
#fragmentelement, causing a mismatch in path-prefix based authorization decisions. - CVE-2021-32779: incorrectly handle duplicate headers, dropping all but the last. This may lead to incorrect routing or authorization policy decisions.
Impact
With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium.
Patches
Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched.
Workarounds
- This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.
References
envoy GSA CVE-2021-32777 envoy GSA CVE-2021-32779 envoy announcement
For more information
If you have any questions or comments about this advisory:
- Open an issue in pomerium/pomerium
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/pomerium/pomerium | ≥ 0.11.0&&< 0.14.8 | 0.14.8 |
| 🐹Go | github.com/pomerium/pomerium | ≥ 0.15.0&&< 0.15.1 | 0.15.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pomerium/pomerium. 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 github.com/pomerium/pomerium to 0.14.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cfc2-wjcm-c8fm 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-cfc2-wjcm-c8fm 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-cfc2-wjcm-c8fm. 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-cfc2-wjcm-c8fm in your dependencies?
O3 detects GHSA-cfc2-wjcm-c8fm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.