CVE-2024-24324
Published: 30 January 2024
Summary
CVE-2024-24324 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Totolink A8000Ru Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique /etc/passwd and /etc/shadow (T1003.008); ranked at the 27.3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
TOTOLINK A8000RU firmware version 7.1cu.643_B20200521 contains a hardcoded root password stored in /etc/shadow. The issue is tracked as CVE-2024-24324 with a CVSS 3.1 score of 9.8 and is classified under CWE-798 for use of hard-coded credentials.
An unauthenticated attacker with network access can authenticate directly as root using the embedded credential. Successful exploitation grants full administrative control over the device, allowing arbitrary command execution and complete compromise of confidentiality, integrity, and availability.
Public disclosure references consist of GitHub repositories that document the hardcoded credential. The EPSS score rose from a low baseline to a peak of 0.0994 on 2025-01-22 before receding to the current value of 0.0010, indicating a period of increased exploitation interest after the initial publication.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-21746
Vulnerability details
TOTOLINK A8000RU v7.1cu.643_B20200521 was discovered to contain a hardcoded password for root stored in /etc/shadow.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Hardcoded root password in /etc/shadow enables dumping credentials from /etc/shadow, accessing unsecured credentials in files, and using valid default/local accounts for unauthorized root access on the device.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Enables users to notice when hard-coded credentials have been exploited for unauthorized access.
Security training explicitly warns against hard-coded credentials, lowering their use in systems.
Policy and procedures prohibit hard-coded credentials in favor of managed authentication.
External identity providers eliminate the need for hard-coded credentials in applications.
Changing default authenticators prior to first use and protecting content prevents use of hard-coded credentials.
Central credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.
Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
Planned investment enables secure credential storage and management systems instead of hard-coded credentials.