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

> Attackers can log in as root using hardcoded credentials in the shadow file, gaining full control of the WAVLINK router.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2024
- **Updated:** 9 Dec 2024
- **Also known as:** GHSA-wc2c-7p6r-2qq8

## What is CVE-2024-54747?

CVE-2024-54747 is a critical vulnerability in n/a, published on 6 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WAVLINK WN531P3 202383 was discovered to contain a hardcoded password vulnerability in /etc/shadow, which allows attackers to log in as root.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Wavlink Wn531p3 Firmware.

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

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

## Is CVE-2024-54747 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54747 is a critical vulnerability in n/a, published on 6 Dec 2024. 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-54747 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-54747/ (Markdown: https://insights.sbomify.com/CVE-2024-54747/index.md)
```

## Sources

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

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