Security Resilience

CVE-2023-41027

Info Disclosure in Juplink Rx4-1500 Firmware 1.0.4 … 1.0.5

Published
22 September 2023
Modified
21 November 2024
CVSS Score v3.1 8.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0089 60th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS 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-41027 is a high-severity Self-generated Error Message Containing Sensitive Information (CWE-210) vulnerability in Juplink Rx4-1500 Firmware. Its CVSS base score is 8.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Search Engines (T1593.002); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Credential disclosure in the '/webs/userpasswd.htm' endpoint in Juplink RX4-1500 Wifi router firmware versions V1.0.4 and V1.0.5 allows an authenticated attacker to leak the password for the administrative account via requests to the vulnerable endpoint.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078.002 Domain Accounts Stealth
Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1589.001 Credentials Reconnaissance
Adversaries may gather credentials that can be used during targeting.
T1589.003 Employee Names Reconnaissance
Adversaries may gather employee names that can be used during targeting.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-41030Same product: Juplink Rx4-1500 Firmware
CVE-2023-41028Same product: Juplink Rx4-1500 Firmware
CVE-2023-41029Same product: Juplink Rx4-1500 Firmware
CVE-2023-41031Same product: Juplink Rx4-1500 Firmware
CVE-2025-25025Shared CWE-209
CVE-2024-41984Shared CWE-209
CVE-2023-23474Shared CWE-209
CVE-2025-9229Shared CWE-209
CVE-2024-52893Shared CWE-209
CVE-2025-20002Shared CWE-209

Affected Assets

juplink
rx4-1500 firmware
1.0.4, 1.0.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

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.

addresses: CWE-209

Detects error messages that leak sensitive information as evidence of disclosure.

addresses: CWE-209

The control directly mitigates generation of error messages containing sensitive authentication details by requiring obscured feedback instead of verbose responses.

addresses: CWE-209

Misdirection allows generation of misleading error messages that withhold or falsify sensitive details.

addresses: CWE-209

Explicitly requires error messages to avoid including sensitive or exploitable details while still supporting corrective action.

addresses: CWE-209

Validation ensures error messages contain only expected, non-sensitive content and blocks leakage via verbose errors.

addresses: CWE-209

Fail-safe procedures can be defined to suppress or sanitize error output, reducing generation of messages that contain sensitive information.

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.

PR.PS-06 mostly match
blocks

Secure SDLC and coding standards directly require proper error handling that avoids leaking sensitive data in messages.

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.

finds

Security testing can detect the weakness but does not prevent it by itself.

prevents

Training makes developers aware that error messages must not leak sensitive information and that exception output should be sanitized, which prevents a minority of instances; the remainder is the same fallible-developer problem that caps A.8.28 against code-level defects like XSS.

finds

Personnel encountering error messages that leak sensitive information could report them under the clause's 'vulnerabilities' or 'breach of confidentiality' categories, but this is a minority share because most instances are never triggered in user-visible error conditions and users typically do not recognize sensitive content in diagnostic output as a security defect to report.

prevents

Secure coding standards directly prohibit embedding sensitive information in generated error messages.

prevents

A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) it contractually requires of the supplier, which would reduce instances of self-generated error messages containing sensitive information in delivered code, but only partially because the clause depends on those other controls being properly implemented and the supplier following them.

prevents

A.8.5 guidance item (c) explicitly prevents log-on error messages from indicating which part of credentials is correct/incorrect, addressing a narrow slice of CWE-210; the vast majority of self-generated error messages containing sensitive information (business logic, file system, database errors elsewhere in the application) are outside the authentication clause's scope.

References