io.socket:socket.io-client: NULL Pointer Dereference
CVE-2022-25867 is a high-severity NULL pointer dereference vulnerability in io.socket:socket.io-client, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.0.1 as the first without the flaw, so updating io.socket:socket.io-client to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.65% chance of exploitation within 30 days, higher than 77% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update io.socket:socket.io-client to 2.0.1 or a later version.
- Update Socket.io-client Java to 2.0.1 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Io.socket:socket.io-client | io.socket:socket.io-client | before 2.0.1 | 2.0.1 |
| Socket | Socket.io-client Java | before 2.0.1 | 2.0.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (snyk.io) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
The package io.socket:socket.io-client before 2.0.1 are vulnerable to NULL Pointer Dereference when parsing a packet with with invalid payload format.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: NULL Pointer Dereference
The product dereferences a pointer that it expects to be valid but is NULL.
How developers prevent this class of flaw
- For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
- Select a programming language that is not susceptible to these issues.
- Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/socketio/socket.io-client-java/commit/8664499b6f31154f49783531f778dac5387b766bThird Party Advisory
- github.com/socketio/socket.io-client-java/commit/e8ffe9d1383736f6a21090ab959a2f4fa5a41284Third Party Advisory
- github.com/socketio/socket.io-client-java/releases/tag/socket.io-client-2.0.1Release Notes, Third Party Advisory
- security.snyk.io/vuln/SNYK-JAVA-IOSOCKET-2949738Exploit, Issue Tracking, Release Notes, Third Party Advisory
Third-party and government advisories
- github.com/socketio/socket.io-client-java/issues/508%23issuecomment-1179817361Third Party Advisory
Recent NULL Pointer Dereference vulnerabilities
- 7.1 High severity
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.