Application crash via malformed XML name scanning
Published Aug 20, 2023 · Updated Aug 2, 2024
Buffer overflow in Qt QXmlStreamReader before 5.15.15, 6.x before 6.2.9, and 6.3.x before 6.5.2 allows attackers to crash applications. The fastScanName() path records a namespace prefix, hits the 4 KiB name limit without updating the value length, and then constructs an XmlStringRef with a negative length. An application must pass attacker-controlled XML to the parser; successful exploitation terminates that application without reported data disclosure or modification.
Summary
What happened
Buffer overflow in Qt QXmlStreamReader before 5.15.15, 6.x before 6.2.9, and 6.3.x before 6.5.2 allows attackers to crash applications. The fastScanName() path records a namespace prefix, hits the 4 KiB name limit without updating the value length, and then constructs an XmlStringRef with a negative length. An application must pass attacker-controlled XML to the parser; successful exploitation terminates that application without reported data disclosure or modification.
The record
- CVE
- CVE-2023-37369
- Published
- Aug 20, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.
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
- QTBUG-114829 crash reproducerproof 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