CVE-2023-41027
Info Disclosure in Juplink Rx4-1500 Firmware 1.0.4 … 1.0.5
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2023-45564
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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
Detects error messages that leak sensitive information as evidence of disclosure.
The control directly mitigates generation of error messages containing sensitive authentication details by requiring obscured feedback instead of verbose responses.
Misdirection allows generation of misleading error messages that withhold or falsify sensitive details.
Explicitly requires error messages to avoid including sensitive or exploitable details while still supporting corrective action.
Validation ensures error messages contain only expected, non-sensitive content and blocks leakage via verbose errors.
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.
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.
Security testing can detect the weakness but does not prevent it by itself.
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.
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.
Secure coding standards directly prohibit embedding sensitive information in generated error messages.
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.
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.