# CVE-2024-12011: Information disclosure in 130.8005

> Remote attackers can leak authentication tokens from the web server memory to bypass authentication on the Zettler TCP/IP Gateway.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-p8r2-h85q-cmcr

## What is CVE-2024-12011?

CVE-2024-12011 is a high-severity vulnerability in Zettler 130.8005, published on 13 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A CWE-126 “Buffer Over-read” was discovered affecting the 130.8005 TCP/IP Gateway running firmware version 12h. The information disclosure can be triggered by leveraging a memory leak affecting the web server. A remote unauthenticated attacker can exploit this vulnerability in order to leak valid authentication tokens from the process memory associated to users currently logged to the system and bypass the authentication mechanism.

Weakness: CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2024-12011?


## How do I fix CVE-2024-12011?

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

## Is CVE-2024-12011 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12011 and fix it if it is affected.

What it is: CVE-2024-12011 is a high-severity vulnerability in Zettler 130.8005, published on 13 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-12011 in the wild and no public exploit code.

Affected product: Zettler 130.8005. 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-2024-12011/ (Markdown: https://insights.sbomify.com/CVE-2024-12011/index.md)
```

## Sources

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

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