GHSA-mg2c-rc36-p594 — trafficcontrol
CRITICALGHSA-mg2c-rc36-p594 is a critical-severity (CVSS 9.8) CWE-90 vulnerability in github.com/apache/trafficcontrol. A fix is available for github.com/apache/trafficcontrol — see the affected versions and patch details below.
Apache Traffic Control Traffic Ops Vulnerable to LDAP Injection
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.
How urgent is this, really
GHSA-mg2c-rc36-p594 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/apache/trafficcontrol🐹github.com/apache/trafficcontrolReal-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
An unauthenticated Apache Traffic Control Traffic Ops user can send a request with a specially-crafted username to the POST /login endpoint of any API version to inject unsanitized content into the LDAP filter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/apache/trafficcontrol | ≥ 6.0.0&&< 6.0.1 | 6.0.1go get github.com/apache/trafficcontrol@v6.0.1 |
| 🐹Go | github.com/apache/trafficcontrol | ≥ 5.1.0&&< 5.1.4 | 5.1.4go get github.com/apache/trafficcontrol@v5.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apache/trafficcontrol, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/apache/trafficcontrol to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mg2c-rc36-p594 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mg2c-rc36-p594 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mg2c-rc36-p594. 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-mg2c-rc36-p594 in your dependencies?
O3 Security finds GHSA-mg2c-rc36-p594 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.