Connman: Out-of-bounds Read
CVE-2022-23096 is a critical-severity out-of-bounds read vulnerability in Connman from Intel, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Connman versions: 1.40 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.6% chance of exploitation within 30 days, higher than 86% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Connman you run against the affected versions below, and install the vendor's latest release.
- 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 |
|---|---|---|---|
| Intel | Connman | 1.40 and earlier | Not stated |
| Debian | Debian Linux | 9.0; 11.0 | Not stated |
Version data comes from NVD's product matching. 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
- HighAll data handled by the component can be read.
- 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:H/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | NVD |
| CVSS 3.1 | 9.1 | Critical | CISA (ADP) |
| CVSS 2.0 | 6.4 | Medium | NVD |
Official description
An issue was discovered in the DNS proxy in Connman through 1.40. The TCP server reply implementation lacks a check for the presence of sufficient Header Data, leading to an out-of-bounds read.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- git.kernel.org/pub/scm/network/connman/connman.git/log/Product, Third Party Advisory
- lists.debian.org/debian-lts-announce/2022/02/msg00009.htmlMailing List, Third Party Advisory
- security.gentoo.org/glsa/202310-21Third Party Advisory
- debian.org/security/2022/dsa-5231Third Party Advisory
Technical write-ups (may include proof of concept)
- openwall.com/lists/oss-security/2022/01/25/1Exploit, Mailing List, Third Party Advisory
Other vulnerabilities in Connman
- 8.1 High severity
- 9.8 Critical severity
Recent Out-of-bounds Read vulnerabilities
- 7.8 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 7.1 High severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.