Code execution via device-name format string
Published May 31, 2022 · Updated Aug 2, 2024
Format string injection in affected freedesktop.org libinput releases beginning with 1.10 allows attackers to execute code via a crafted device name. In src/evdev.c, a device name becomes part of a log format string that caller-installed handlers commonly pass to printf without neutralizing directives. Exploitation requires control of a kernel input-device name through a facility such as /dev/uinput or Bluetooth, and code runs with the caller's privileges, which can be root under X.Org.
Summary
What happened
Format string injection in affected freedesktop.org libinput releases beginning with 1.10 allows attackers to execute code via a crafted device name. In src/evdev.c, a device name becomes part of a log format string that caller-installed handlers commonly pass to printf without neutralizing directives. Exploitation requires control of a kernel input-device name through a facility such as /dev/uinput or Bluetooth, and code runs with the caller's privileges, which can be root under X.Org.
The record
- CVE
- CVE-2022-1215
- Published
- May 31, 2022
- Updated
- Aug 2, 2024
- Vendor
- Libslirp Project
- Product
- libinput
- Classifications
- CWE-134, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=libinput 1.10 and above
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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