# CVE-2024-29071: Hardcoded credentials in HGW BL1500HM

> An unauthenticated network-adjacent attacker can change system settings on the HGW BL1500HM home gateway due to weak credentials.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-8jm2-4r4f-748v

## What is CVE-2024-29071?

CVE-2024-29071 is a high-severity vulnerability in KDDI CORPORATION HGW BL1500HM, published on 25 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HGW BL1500HM Ver 002.001.013 and earlier contains a use of week credentials issue. A network-adjacent unauthenticated attacker may change the system settings.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2024-29071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29071 is a high-severity vulnerability in KDDI CORPORATION HGW BL1500HM, published on 25 Mar 2024. 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-2024-29071 in the wild and no public exploit code.

Affected product: KDDI CORPORATION HGW BL1500HM. 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-29071/ (Markdown: https://insights.sbomify.com/CVE-2024-29071/index.md)
```

## Sources

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

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