# CVE-2025-24034: Himmelblau leaks credentials in the debug log

> Himmelblau leaks user access tokens and Kerberos TGTs in debug logs, exposing sensitive credentials to attackers with log access.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-p989-2f5w-9cf6

## What is CVE-2025-24034?

CVE-2025-24034 is a low-severity vulnerability in himmelblau-idm himmelblau, published on 23 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. Starting in version 0.7.0 and prior to versions 0.7.15 and 0.8.3, Himmelblau is vulnerable to leaking credentials in debug logs. When debug logging is enabled, user access tokens are inadvertently logged, potentially exposing sensitive authentication data. Similarly, Kerberos Ticket-Granting Tickets (TGTs) are logged when debug logging is enabled. Both issues pose a risk of exposing sensitive credentials, particularly in environments where debug logging is enabled. Himmelblau versions 0.7.15 and 0.8.3 contain a patch that fixes both issues. Some workarounds are available for users who are unable to upgrade. For the **logon compliance script issue**, disable the `logon_script` option in `/etc/himmelblau/himmelblau.conf`, and avoid using the `-d` flag when starting the `himmelblaud` daemon. For the Kerberos CCache issue, one may disable debug logging globally by setting the `debug` option in `/etc/himmelblau/himmelblau.conf` to `false` and avoiding the `-d` parameter when starting `himmelblaud`.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-24034?


## How do I fix CVE-2025-24034?

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

## Is CVE-2025-24034 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24034 and fix it if it is affected.

What it is: CVE-2025-24034 is a low-severity vulnerability in himmelblau-idm himmelblau, published on 23 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24034 in the wild and no public exploit code.

Affected product: himmelblau-idm himmelblau. 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-2025-24034/ (Markdown: https://insights.sbomify.com/CVE-2025-24034/index.md)
```

## Sources

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

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