# CVE-2019-12405: Improper Authentication in Apache Traffic Control

> Attackers can bypass authentication in Apache Traffic Control's Traffic Ops API when LDAP is enabled, allowing unauthorized access as any valid user.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3f8r-4qwm-r7jf

## What is CVE-2019-12405?

CVE-2019-12405 is a critical authentication bypass vulnerability in Apache Traffic Control, published on 9 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-12405?

2 open source packages ship an affected version, including github.com/apache/trafficcontrol. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/apache/trafficcontrol` | Go | From 3.0.0 | 3.0.2-RC1 |
| `github.com/apache/trafficcontrol` | Go | From 3.0.0 | 3.0.2-RC1 |

Products: Apache Traffic Control.

## How do I fix CVE-2019-12405?

Upgrade github.com/apache/trafficcontrol to 3.0.2-RC1 or later.

## Is CVE-2019-12405 being exploited?

There is no known exploitation of CVE-2019-12405 in the wild and no public exploit code.

## Other vulnerabilities in Apache Traffic Control

- [CVE-2024-45387](https://insights.sbomify.com/CVE-2024-45387/): Apache Traffic Control: SQL Injection in Traffic Ops endpoint PUT deliveryservice_request_comments (critical 9.9)
- [CVE-2021-43350](https://insights.sbomify.com/CVE-2021-43350/): LDAP filter injection vulnerability in Traffic Ops (critical 9.8)
- [CVE-2025-61581](https://insights.sbomify.com/CVE-2025-61581/): Apache Traffic Control: ReDoS issue in Traffic Router configuration (high 7.5)
- [CVE-2022-23206](https://insights.sbomify.com/CVE-2022-23206/): Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth (high 7.5)
- [CVE-2017-7670](https://insights.sbomify.com/CVE-2017-7670/): Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12405 and fix it if it is affected.

What it is: CVE-2019-12405 is a critical authentication bypass vulnerability in Apache Traffic Control, published on 9 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12405 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/apache/trafficcontrol (Go): affected from 3.0.0; fixed in 3.0.2-RC1
- github.com/apache/trafficcontrol (Go): affected from 3.0.0; fixed in 3.0.2-RC1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-12405/ (Markdown: https://insights.sbomify.com/CVE-2019-12405/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12405
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12405
- OSV: https://osv.dev/vulnerability/CVE-2019-12405

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-12405/
Summaries are generated and may contain mistakes; the official description above is the record.