Client crash via unchecked event payload
Published Aug 2, 2022 · Updated Sep 16, 2024
Null pointer dereference in Socket.IO Client Java before 2.0.1 allows remote attackers to crash client applications via malformed event payloads. IOParser.decodeString accepts an EVENT or BINARY_EVENT payload whose array is empty or begins with null, then Socket.onevent calls toString on the missing first element. A server able to send such a packet can terminate the client's event thread and interrupt the embedding application.
Summary
What happened
Null pointer dereference in Socket.IO Client Java before 2.0.1 allows remote attackers to crash client applications via malformed event payloads. IOParser.decodeString accepts an EVENT or BINARY_EVENT payload whose array is empty or begins with null, then Socket.onevent calls toString on the missing first element. A server able to send such a packet can terminate the client's event thread and interrupt the embedding application.
The record
- CVE
- CVE-2022-25867
- Published
- Aug 2, 2022
- Updated
- Sep 16, 2024
- Vendor
- Socket.IO
- Product
- Socket.IO Client Java
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 2, 2022CVE 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 <2.0.1
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
No public exploit references are available in this record.
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