Driver crash via null cookie-name dereference
Published Oct 15, 2023 · Updated Sep 16, 2024
Null pointer dereference in Selenium before 4.14.0 allows remote attackers to crash IE Driver during cookie retrieval from a crafted page. CookieWndProc constructs a C++ std::wstring directly from an INTERNETCOOKIE2 pwszName pointer without first checking whether the name pointer is null. Exposure requires a WebDriver session using IE Driver or Edge IE mode to retrieve cookies from an attacker-controlled page; the documented consequence is an IE Driver crash, not data access or modification.
Summary
What happened
Null pointer dereference in Selenium before 4.14.0 allows remote attackers to crash IE Driver during cookie retrieval from a crafted page. CookieWndProc constructs a C++ std::wstring directly from an INTERNETCOOKIE2 pwszName pointer without first checking whether the name pointer is null. Exposure requires a WebDriver session using IE Driver or Edge IE mode to retrieve cookies from an attacker-controlled page; the documented consequence is an IE Driver crash, not data access or modification.
The record
- CVE
- CVE-2023-5590
- Published
- Oct 15, 2023
- Updated
- Sep 16, 2024
- Vendor
- Selenium
- Product
- Selenium
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2023CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <4.14.0
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
- huntr.dev bounty proof of conceptproof 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