Remote CPU exhaustion via persistent writable socket
Published Jan 28, 2022 · Updated Aug 3, 2024
Denial of service in ConnMan through 1.40 allows remote attackers to exhaust CPU through a nonresponsive TCP DNS server. In dnsproxy.c's TCP server reply path, the G_IO_OUT watch remains registered after a nonblocking connection succeeds, so the main loop continuously wakes on the writable socket. Exploitation requires ConnMan to connect to an attacker-controlled DNS server that keeps the TCP connection open without returning data, causing sustained 100% CPU use rather than a crash.
Summary
What happened
Denial of service in ConnMan through 1.40 allows remote attackers to exhaust CPU through a nonresponsive TCP DNS server. In dnsproxy.c's TCP server reply path, the G_IO_OUT watch remains registered after a nonblocking connection succeeds, so the main loop continuously wakes on the writable socket. Exploitation requires ConnMan to connect to an attacker-controlled DNS server that keeps the TCP connection open without returning data, causing sustained 100% CPU use rather than a crash.
The record
- CVE
- CVE-2022-23098
- Published
- Jan 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-835, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- TCP DNS non-response busy-loop proof of conceptproof of concept · demonstrated
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