# CVE-2024-31151: Hardcoded credentials in WBR-6012

> Attackers can gain unauthorized user-level access to LevelOne WBR-6012 routers using a hard-coded password available during the first 30 seconds after boot.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 30 Oct 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-q63q-pqgx-268p

## What is CVE-2024-31151?

CVE-2024-31151 is a high-severity vulnerability in LevelOne WBR-6012, published on 30 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw involving hard-coded credentials in LevelOne WBR-6012's web services allows attackers to gain unauthorized access during the first 30 seconds post-boot. Other vulnerabilities can force a reboot, circumventing the initial time restriction for exploitation.The password string can be found at addresses 0x 803cdd0f and 0x803da3e6:

    803cdd0f 41 72 69 65        ds         "AriesSerenaCairryNativitaMegan"
             73 53 65 72 
             65 6e 61 43
             ...

It is referenced by the function at 0x800b78b0 and simplified in the pseudocode below:

    if (is_equal = strcmp(password,"AriesSerenaCairryNativitaMegan"){
        ret = 3;}

Where 3 is the return value to user-level access (0 being fail and 1 being admin/backdoor).

While there's no legitimate functionality to change this password, once authenticated it is possible manually make a change by taking advantage of TALOS-2024-XXXXX using HTTP POST paramater "Pu" (new user password) in place of "Pa" (new admin password).

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Level1 Wbr-6012 Firmware.

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

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

## Is CVE-2024-31151 being exploited?

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

## Other vulnerabilities in LevelOne WBR-6012

- [CVE-2024-33699](https://insights.sbomify.com/CVE-2024-33699/): Auth bypass in WBR-6012 (critical 9.9)
- [CVE-2024-23309](https://insights.sbomify.com/CVE-2024-23309/): Auth bypass in WBR-6012 (critical 9.0)
- [CVE-2024-24777](https://insights.sbomify.com/CVE-2024-24777/): Cross-site request forgery in WBR-6012 (high 8.8)
- [CVE-2024-28875](https://insights.sbomify.com/CVE-2024-28875/): Hardcoded credentials in WBR-6012 (high 8.1)
- [CVE-2024-33700](https://insights.sbomify.com/CVE-2024-33700/): Denial of service in WBR-6012 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31151 is a high-severity vulnerability in LevelOne WBR-6012, published on 30 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31151 in the wild and no public exploit code.

Affected product: LevelOne WBR-6012. 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-31151/ (Markdown: https://insights.sbomify.com/CVE-2024-31151/index.md)
```

## Sources

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

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