Daemon crash via NULL device-path matching
Published May 26, 2021 · Updated Aug 3, 2024
Improper input validation in Red Hat NetworkManager before 1.30.0 allows local users to crash the daemon by activating a match.path profile. During profile matching, nm_wildcard_match_check() treats an absent device path as a string and dereferences the NULL value. Low-privileged local access is required, and the resulting daemon crash interrupts network management and can disrupt managed connectivity.
Summary
What happened
Improper input validation in Red Hat NetworkManager before 1.30.0 allows local users to crash the daemon by activating a match.path profile. During profile matching, nm_wildcard_match_check() treats an absent device path as a string and dereferences the NULL value. Low-privileged local access is required, and the resulting daemon crash interrupts network management and can disrupt managed connectivity.
The record
- CVE
- CVE-2021-20297
- Published
- May 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- NetworkManager
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=NetworkManager 1.30.0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
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