CVE-2023-41030
Exposed Creds in Juplink Rx4-1500 Firmware 1.0.2 – 1.0.5
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41030 is a medium-severity Use of Hard-coded Password (CWE-259) vulnerability in Juplink Rx4-1500 Firmware. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-45567
Vulnerability Data
Hard-coded credentials in Juplink RX4-1500 versions V1.0.2 through V1.0.5 allow unauthenticated attackers to log in to the web interface or telnet service as the 'user' user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls
Our mappings. 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.
Changing default authenticators prior to first use directly prevents use of hard-coded passwords.
Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
Vetting reduces the chance a developer will deliberately insert hard-coded credentials as a backdoor or unauthorized access mechanism.
Supplier risk reviews identify and discourage hard-coded credentials in delivered products or services.
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.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prohibit embedding credentials in source code or binaries.
PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's SOURCE+RUNTIME reach finds hard-coded passwords well: SAST detects password string literals, code review catches them, and penetration testing extracts them from binaries; the same bounded remainder as the CWE-798 anchor applies -- credentials assembled at build time, baked into images as configuration, or shipped inside binary-only third-party components.
Training/awareness addresses hard-coded passwords as a known anti-pattern (the clause explicitly names password security as a baseline control topic), and a developer who has been educated will sometimes choose not to hard-code credentials, but the weakness is a code-level defect introduced during implementation where convenience pressures and time-to-market routinely override training, so the effect is a minority one.
Network segregation can prevent untrusted domains from reaching an inbound authentication interface that uses a hard-coded password, but it leaves the credential exploitable from permitted network paths and does not prevent reuse of outbound hard-coded passwords.
A.8.24's key management guidance (generation, storage, distribution through proper processes) prevents hard-coded cryptographic keys in first-party code, but the clause addresses cryptography, not authentication credentials, so the password variant of CWE-798 is untouched; third-party and COTS components with embedded credentials are also outside its reach.
A.8.28 explicitly prohibits hard-coded passwords in its 'During coding' guidance (item e), so a system under the clause sees fewer instances arise, but the clause mandates a practice rather than a mechanism and the prohibition depends on developer compliance, third-party components, and the rigour of implementation — the same ceiling the owner set for A.8.28 on CWE-502 and CWE-79.
A.8.30's programme includes acceptance testing (item d) and contractual audit rights (item i), which can surface hard-coded passwords in delivered code, but these are a minority of instances — most are caught by the supplier's own development-time testing (A.8.29), which A.8.30 only requires contractually rather than performs itself.