CVE-2024-31151
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHard-coded credentials vulnerability in LevelOne WBR-6012 router's web interface allows unauthenticated attackers to gain user-level access using the static password 'AriesSerenaCairryNativitaMegan' during the first 30 seconds post-boot. Attackers can force a device reboot using other vulnerabilities (TALOS-2024-XXXXX) to circumvent the time restriction. The password is embedded at memory addresses 0x803cdd0f and 0x803da3e6 and is checked by the function at 0x800b78b0, returning 3 for user access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= r0.40e6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface, or SNMP for model number WBR-6012 from LevelOne/Level1Affected if Device is a LevelOne WBR-6012 router
-
Check the firmware versionAccess the router's web interface (typically at 192.168.0.1) and look in the firmware/version settings, or use 'nvram show' or 'cat /proc/version' via telnet/SSH if availableAffected if Firmware version is r0.40e6
-
Verify the hardcoded password exists in firmwareDownload the firmware binary from the vendor site and search for the string 'AriesSerenaCairryNativitaMegan' using strings or hexdump (e.g., strings firmware.bin | grep -i Aries)Affected if The password string is found embedded in the firmware binary
-
Check device uptimeLog into the device and run 'uptime' command or check the system status page in the web interface to see seconds since last rebootAffected if Device has been running for less than 30 seconds (first boot window)
-
Test the hardcoded credentialAttempt to log into the router's web interface or telnet/SSH using the username 'admin' and password 'AriesSerenaCairryNativitaMegan'Affected if Login succeeds with this static credential
A user is affected if they have a LevelOne WBR-6012 router running firmware r0.40e6 and the hardcoded password 'AriesSerenaCairryNativitaMegan' is present in the firmware binary.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThis is a critical firmware-level flaw in an end-of-life router with no legitimate mechanism to change the hardcoded password. Organizations should immediately segment affected devices from sensitive networks, replace with supported hardware, and monitor for unauthorized access attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-31151 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data