# CVE-2024-54767: Information disclosure in n/a

> Attackers can access sensitive information via an unauthenticated endpoint on AVM FRITZ!Box routers when exposed directly to the internet.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2025
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-fmmw-r3g8-j32w

## What is CVE-2024-54767?

CVE-2024-54767 is a high-severity vulnerability in n/a, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An access control issue in the component /juis_boxinfo.xml of AVM FRITZ!Box 7530 AX v7.59 allows attackers to obtain sensitive information without authentication. NOTE: this is disputed by the Supplier because it cannot be reproduced, and the issue report focuses on an unintended configuration with direct Internet exposure.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2024-54767 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54767 exists.

Public exploit code:

- Research & PoC for CVE-2024-54767 and related unauthenticated FRITZ!OS information-disclosure findings across multiple FRITZ!Box models and firmware versions. (github_poc): https://github.com/lowlevelsec/AVM-FRITZ-Box-CVE-2024-54767-Exploit
- AVM FRITZ!Box 7530 AX - Unauthorized Access (nuclei): http/cves/2024/CVE-2024-54767.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54767 is a high-severity vulnerability in n/a, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54767 exists.

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

## Sources

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

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