Validation bypass via post-check Unicode normalization
Published Sep 15, 2023 · Updated Sep 25, 2024
Improper Unicode handling in SHIRASAGI before 1.18.0 allows remote attackers to bypass blank-name validation via crafted input. Rdf::Object#normalize_name checks whether a name is blank before NFKC normalization, allowing Unicode whitespace to become an unchecked blank value or surviving spaces. Network access without authentication is sufficient, and the demonstrated consequence is integrity loss through acceptance of names that validation intended to reject.
Summary
What happened
Improper Unicode handling in SHIRASAGI before 1.18.0 allows remote attackers to bypass blank-name validation via crafted input. Rdf::Object#normalize_name checks whether a name is blank before NFKC normalization, allowing Unicode whitespace to become an unchecked blank value or surviving spaces. Network access without authentication is sufficient, and the demonstrated consequence is integrity loss through acceptance of names that validation intended to reject.
The record
- CVE
- CVE-2023-41889
- Published
- Sep 15, 2023
- Updated
- Sep 25, 2024
- Vendor
- SHIRASAGI Project
- Product
- SHIRASAGI
- Classifications
- CWE-176
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.18.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GHSA Unicode-normalization proof of conceptproof 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