CVE-2024-31151VulnerabilityPublished 30 Oct 2024Updated 3 Nov 2025

CVE-2024-31151: LevelOne WBR-6012 · Use of Hard-coded Credentials

Affects LevelOne WBR-6012Source CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediate mitigation should focus on network-level controls: isolate affected WBR-6012 devices from untrusted networks and restrict management access to trusted administrators only. Implement strict firewall rules to block external access to router web services. Monitor network traffic for unusual reboot patterns that may indicate exploitation attempts. Disable remote management features if not required. Where possible, replace affected devices with models from vendors that do not have hard-coded credentials. If replacement is not feasible, consider deploying network segmentation and intrusion detection systems to detect and contain exploitation attempts. Since no official patches are available, coordinate with LevelOne for firmware updates or advisories. Additionally, conduct regular audits of device configurations and credentials, and educate staff about the risks of using devices with known hard-coded credentials. Finally, prepare incident response plans specific to router compromise scenarios to minimize impact if exploitation occurs.

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).

Impact

For European organizations, this vulnerability poses significant risks including unauthorized access to network devices, potential interception or manipulation of network traffic, and disruption of network services. Compromise of the WBR-6012 routers could allow attackers to pivot into internal networks, exfiltrate sensitive data, or launch further attacks such as man-in-the-middle or denial-of-service. The ability to force reboots to bypass the initial time restriction increases the attack surface and persistence potential. Organizations relying on these routers in critical infrastructure, small to medium enterprises, or branch offices may face operational disruptions and data breaches. The lack of available patches means that affected entities must rely on compensating controls, increasing operational complexity and risk. Additionally, the exposure of hard-coded credentials undermines trust in device security and may lead to regulatory compliance issues under GDPR if personal data is compromised.

Summary

CVE-2024-31151 identifies a critical security flaw in the LevelOne WBR-6012 router, specifically firmware version R0.40e6. The vulnerability stems from the presence of a hard-coded password embedded directly in the device's web services binary at memory addresses 0x803cdd0f and 0x803da3e6. The password string "AriesSerenaCairryNativitaMegan" is used by the authentication function to grant user-level access immediately after device boot, within a 30-second window. This time-limited access is intended to restrict exploitation; however, other vulnerabilities allow attackers to force device reboots, effectively resetting the timer and enabling repeated unauthorized access. The authentication function returns a value of 3 upon successful password match, granting user-level privileges, while 0 indicates failure and 1 indicates admin or backdoor access. Although the hard-coded password cannot be changed through normal means, attackers who gain access can exploit an additional vulnerability (TALOS-2024-XXXXX) to change user passwords by sending specially crafted HTTP POST requests with the "Pu" parameter. The vulnerability is remotely exploitable without prior authentication or user interaction, and the CVSS 3.1 base score of 8.1 reflects its high impact on confidentiality, integrity, and availability. No official patches are currently available, increasing the urgency for mitigation. The flaw exposes devices to unauthorized control, potential data leakage, and service disruption, especially in environments where these routers are deployed in critical network segments.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:59 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats