USB policy bypass via unchecked D-Bus methods
Published Feb 24, 2022 · Updated Aug 5, 2024
Incorrect authorization in USBGuard before 1.1.0 allows local users to permit future USB device connections through D-Bus. The usbguard-dbus service exposes parameter methods without Polkit authorization checks, while an invalid Polkit action value causes the policy file to be ignored. An unprivileged local account can set InsertedDevicePolicy to an allowing mode, weakening USB controls for subsequently connected hardware.
Summary
What happened
Incorrect authorization in USBGuard before 1.1.0 allows local users to permit future USB device connections through D-Bus. The usbguard-dbus service exposes parameter methods without Polkit authorization checks, while an invalid Polkit action value causes the policy file to be ignored. An unprivileged local account can set InsertedDevicePolicy to an allowing mode, weakening USB controls for subsequently connected hardware.
The record
- CVE
- CVE-2019-25058
- Published
- Feb 24, 2022
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- Unprivileged D-Bus parameter access demonstrationproof 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