# CVE-2019-12452: Containous Traefik Exposes Password Hashes

> Authenticated users can expose password hashes and keys via the API if it is publicly accessible without proper access control.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r3fq-cmmw-cpmm, GO-2023-1919

## What is CVE-2019-12452?

CVE-2019-12452 is a high-severity vulnerability in Traefik Traefik, published on 29 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

types/types.go in Containous Traefik 1.7.x through 1.7.11, when the --api flag is used and the API is publicly reachable and exposed without sufficient access control (which is contrary to the API documentation), allows remote authenticated users to discover password hashes by reading the Basic HTTP Authentication or Digest HTTP Authentication section, or discover a key by reading the ClientTLS section. These can be found in the JSON response to a /api request.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

3 open source packages ship an affected version, including github.com/traefik/traefik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/traefik/traefik` | Go | From 1.7.0 | 1.7.12 |
| `github.com/traefik/traefik` | Go | From 1.7.0 | 1.7.12 |
| `github.com/traefik/traefik` | Go | From 1.7.0 | 1.7.12 |

Products: Traefik Traefik.

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

Upgrade github.com/traefik/traefik to 1.7.12 or later.

## Is CVE-2019-12452 being exploited?

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

## Other vulnerabilities in Traefik Traefik

- [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8)
- [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3)
- [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3)
- [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1)
- [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12452 is a high-severity vulnerability in Traefik Traefik, published on 29 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12452 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/traefik/traefik (Go): affected from 1.7.0; fixed in 1.7.12
- github.com/traefik/traefik (Go): affected from 1.7.0; fixed in 1.7.12
- github.com/traefik/traefik (Go): affected from 1.7.0; fixed in 1.7.12

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-12452/ (Markdown: https://insights.sbomify.com/CVE-2019-12452/index.md)
```

## Sources

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

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