Local socket hijacking via attacker-controlled directory
Published Sep 7, 2022 · Updated Sep 17, 2024
Improper access control in affected canna packages for openSUSE Backports SLE 15 SP3 and SP4 allows local users to hijack its UNIX socket. The systemd service places .iroha_unix under attacker-writable /tmp, allowing a local user to substitute a bogus directory before socket creation. The attacker can intercept or impersonate local canna client connections, exposing or altering their data without user interaction.
Summary
What happened
Improper access control in affected canna packages for openSUSE Backports SLE 15 SP3 and SP4 allows local users to hijack its UNIX socket. The systemd service places .iroha_unix under attacker-writable /tmp, allowing a local user to substitute a bogus directory before socket creation. The attacker can intercept or impersonate local canna client connections, exposing or altering their data without user interaction.
The record
- CVE
- CVE-2022-21950
- Published
- Sep 7, 2022
- Updated
- Sep 17, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Backports SLE-15-SP3
- Classifications
- CWE-284, T1557
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=canna <canna-3.7p3-bp153.2.3.1
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