CVE-2023-43261
Published: 04 October 2023
Summary
CVE-2023-43261 is a high-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Milesight Ur5X Firmware. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2023-43261 is an information disclosure vulnerability present in Milesight UR5X, UR32L, UR32, UR35, and UR41 routers before firmware version 35.3.0.7. The issue, tracked as CWE-532, allows unauthenticated remote access to sensitive router components and is rated 7.5 under CVSS 3.1 for its network attack vector, low complexity, and high confidentiality impact.
An attacker with network access can exploit the flaw to retrieve credentials and other internal data without authentication or user interaction. Public proof-of-concept code and write-ups confirm the attack path leads to credential leakage from the affected industrial routers.
Firmware version 35.3.0.7 and later resolve the exposure. The vendor site and associated advisories direct users to apply the update for the listed models.
The vulnerability shows a sustained high EPSS score of 0.9314 with matching peak value, and multiple public references including exploit code on GitHub and Packet Storm indicate active research interest following disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-47680
Vulnerability details
An information disclosure in Milesight UR5X, UR32L, UR32, UR35, UR41 before v35.3.0.7 allows attackers to access sensitive router components.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
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.
Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.
Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.
Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.
Identifying logging as a data action allows prevention of sensitive information being inserted into log files.
The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.
Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.
PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.
Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.