Access restriction bypass via late Unicode normalization
Published Dec 15, 2023 · Updated Oct 8, 2024
Improper Unicode handling in Classic LOCKSS Daemon before 1.77.3 allows remote attackers to bypass intended access restrictions. The cleanName() function removes forbidden characters before NFC normalization, allowing normalization of U+1FEF to reintroduce a backtick. No authentication or user interaction is required; the documented consequence is limited to bypassing character-based restrictions.
Summary
What happened
Improper Unicode handling in Classic LOCKSS Daemon before 1.77.3 allows remote attackers to bypass intended access restrictions. The cleanName() function removes forbidden characters before NFC normalization, allowing normalization of U+1FEF to reintroduce a backtick. No authentication or user interaction is required; the documented consequence is limited to bypassing character-based restrictions.
The record
- CVE
- CVE-2023-42183
- Published
- Dec 15, 2023
- Updated
- Oct 8, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-116, CWE-176
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2023CVE publishedPublication date reported by the CVE source.
- Oct 8, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- U+1FEF post-normalization demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo