Local service interruption via file descriptor leak
Published Jun 8, 2020 · Updated Aug 4, 2024
Resource exhaustion in D-Bus 1.3.0 through 1.12.17 allows local users to interrupt dbus-daemon service through a Unix socket. When _dbus_read_socket_with_unix_fds encounters truncated control data, it returns an error without closing file descriptors already received. Access to the system bus or a system service's private AF_UNIX socket is required; repetition exhausts RLIMIT_NOFILE and blocks subsequent clients.
Summary
What happened
Resource exhaustion in D-Bus 1.3.0 through 1.12.17 allows local users to interrupt dbus-daemon service through a Unix socket. When _dbus_read_socket_with_unix_fds encounters truncated control data, it returns an error without closing file descriptors already received. Access to the system bus or a system service's private AF_UNIX socket is required; repetition exhausts RLIMIT_NOFILE and blocks subsequent clients.
The record
- CVE
- CVE-2020-12049
- Published
- Jun 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-404, T1499.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- D-Bus file descriptor leak 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