# CVE-2019-12494: Missing authorization in n/a

> Attackers can access data from other clusters by sending HTTP requests through the VPN endpoint due to missing access controls in Gardener.

- **Severity:** High 8.5 (`CVSS:3.0/AC:H/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9j69-f6q8-h6wm

## What is CVE-2019-12494?

CVE-2019-12494 is a high-severity missing authorization vulnerability in n/a, published on 5 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Gardener before 0.20.0, incorrect access control in seed clusters allows information disclosure by sending HTTP GET requests from one's own shoot clusters to foreign shoot clusters. This occurs because traffic from shoot to seed via the VPN endpoint is not blocked.

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

It affects 1 product.


Products: Gardener Gardener.

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

No fix has been published for CVE-2019-12494 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-12494 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-47283](https://insights.sbomify.com/CVE-2025-47283/): Bypassing project secret validation can lead to privilege escalation (critical 9.9)
- [CVE-2025-47284](https://insights.sbomify.com/CVE-2025-47284/): Gardener vulnerable to metadata injection for a project secret that can lead to privilege escalation (critical 9.9)
- [CVE-2018-2475](https://insights.sbomify.com/CVE-2018-2475/): Missing authorization in project “Gardener” (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12494 is a high-severity missing authorization vulnerability in n/a, published on 5 Jun 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-12494 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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