# CVE-2024-12012: Information disclosure in 130.8005

> Attackers can leak password hashes and session tokens via URL exposure, enabling authentication bypass through pass-the-hash attacks on the gateway.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-rxrj-c86x-c8c8

## What is CVE-2024-12012?

CVE-2024-12012 is a medium-severity vulnerability in Zettler 130.8005, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A CWE-598 “Use of GET Request Method with Sensitive Query Strings” was discovered affecting the 130.8005 TCP/IP Gateway running firmware version 12h. Both the SHA-1 hash of the password as well as the session tokens are included as part of the URL and therefore exposed to information leakage scenarios. An attacker capable of accessing such values (e.g., victim browser, network traffic inspection) can exploit this vulnerability to leak both the password hash as well as session tokens and bypass the authentication mechanism using a pass-the-hash attack.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

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


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

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

## Is CVE-2024-12012 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12012 is a medium-severity vulnerability in Zettler 130.8005, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-12012 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-12012/ (Markdown: https://insights.sbomify.com/CVE-2024-12012/index.md)
```

## Sources

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

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