Crash and memory disclosure via CSS type confusion
Published Feb 8, 2020 · Updated Aug 6, 2024
Type confusion in Konqueror 4.7.3's KHTML CSS parser allows remote attackers to crash the browser or read process memory via crafted CSS. In khtml/css/cssparser.cpp, font-face source handling treats format() and local() values as an incompatible internal type, corrupting memory. Exploitation requires a user to open attacker-controlled web content; the bounded results are process termination and disclosure of memory visible to the browser.
Summary
What happened
Type confusion in Konqueror 4.7.3's KHTML CSS parser allows remote attackers to crash the browser or read process memory via crafted CSS. In khtml/css/cssparser.cpp, font-face source handling treats format() and local() values as an incompatible internal type, corrupting memory. Exploitation requires a user to open attacker-controlled web content; the bounded results are process termination and disclosure of memory visible to the browser.
The record
- CVE
- CVE-2012-4512
- Published
- Feb 8, 2020
- Updated
- Aug 6, 2024
- Vendor
- KDE
- Product
- Konqueror
- Classifications
- CWE-843, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=4.7.3
What conditions does exploitation require?
What is affected?
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
- Konqueror 4.7.3 Memory Corruptionproof of concept · unverified
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