# CVE-2024-48272: Hardcoded credentials in n/a

> Attackers can brute-force the insecure default Wi-Fi password to gain unauthorized access to the D-Link router.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-5qhh-w7j8-f42j

## What is CVE-2024-48272?

CVE-2024-48272 is a medium-severity vulnerability in n/a, published on 30 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DSL6740C v6.TR069.20211230 was discovered to use an insecure default Wifi password, possibly allowing attackers to connect to the device via a bruteforce attack.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Dlink Dsl-6740c Firmware.

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

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

## Is CVE-2024-48272 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-48271](https://insights.sbomify.com/CVE-2024-48271/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48272 is a medium-severity vulnerability in n/a, published on 30 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48272 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-48272/ (Markdown: https://insights.sbomify.com/CVE-2024-48272/index.md)
```

## Sources

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

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