Connman
Vendor:
First CVE: Jan 1, 2013 · Active for 13 years
10
Total CVEs
More Total CVEs than 88% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 60% of tracked products
8.0
Avg CVSS
Higher Avg CVSS than 68% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Connman over time
Volume of CVEsAvg CVSS Base Score
First CVE
Jan 1, 2013
13 years ago
Most Recent CVE
Apr 12, 2023
1,199 days ago
CVE Severity & Scoring
Connman10 CVEs
30%
30%
40%
All CVEs352,231 CVEs
45%
40%
11%
MediumHighCritical
Attack Vector
Local0 (0.0%)
Network6 (60.0%)
Unknown1 (10.0%)
Physical0 (0.0%)
Adjacent Network3 (30.0%)
Attack Complexity
Low8 (80.0%)
High1 (10.0%)
Unknown1 (10.0%)
User Interaction
None9 (90.0%)
Unknown1 (10.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None9 (90.0%)
Unknown1 (10.0%)
Top CVEs
Signals from CVEs in this product scope (10 CVEs).
10 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-32292CRITICAL In ConnMan through 1.41, remote attackers able to send HTTP requests to the gweb component are able to exploit a heap-based buffer overflow in received_data to execute code. | Aug 3, 2022 | 9.8 | 33 | NO | NO |
CVE-2017-12865CRITICAL Stack-based buffer overflow in "dnsproxy.c" in connman 1.34 and earlier allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a crafted respons | Aug 29, 2017 | 9.8 | 33 | NO | NO |
CVE-2022-23096CRITICAL 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 | Jan 28, 2022 | 9.1 | 31 | NO | NO |
CVE-2022-23097CRITICAL An issue was discovered in the DNS proxy in Connman through 1.40. forward_dns_reply mishandles a strnlen call, leading to an out-of-bounds read. | Jan 28, 2022 | 9.1 | 30 | NO | NO |
CVE-2021-26675HIGH A stack-based buffer overflow in dnsproxy in ConnMan before 1.39 could be used by network adjacent attackers to execute code. | Feb 9, 2021 | 8.8 | 28 | NO | NO |
CVE-2022-32293HIGH In ConnMan through 1.41, a man-in-the-middle attack against a WISPR HTTP query could be used to trigger a use-after-free in WISPR handling, leading to crashes or code execution. | Aug 3, 2022 | 8.1 | 27 | NO | NO |
CVE-2022-23098HIGH An issue was discovered in the DNS proxy in Connman through 1.40. The TCP server reply implementation has an infinite loop if no data is received. | Jan 28, 2022 | 7.5 | 27 | NO | NO |
CVE-2023-28488MEDIUM client.c in gdhcp in ConnMan through 1.41 could be used by network-adjacent attackers (operating a crafted DHCP server) to cause a stack-based buffer overflow and denial of service | Apr 12, 2023 | 6.5 | 22 | NO | NO |
CVE-2021-26676MEDIUM gdhcp in ConnMan before 1.39 could be used by network-adjacent attackers to leak sensitive stack information, allowing further exploitation of bugs in gdhcp. | Feb 9, 2021 | 6.5 | 22 | NO | NO |
CVE-2012-6459MEDIUM ConnMan 1.3 on Tizen continues to list the bluetooth service after offline mode has been enabled, which might allow remote attackers to obtain sensitive information via Bluetooth p | Jan 1, 2013 | 4.3 | 17 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (10 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (10 CVEs).
Media Mentions
Signals from CVEs in this product scope (10 CVEs).
Top CNAs Publishing CVEs For Connman
Top CWEs
Versions
| Version | CVE Count | Avg CVSS | Avg EPSS | KEV | Exploits |
|---|---|---|---|---|---|
| 1.3 | 1 | 4.3 | 1.1% | 0 | 0 |