Networkmanager-libreswan: local privilege escalation via leftupdown
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.2.24
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in the libreswan client plugin for NetworkManager (NetkworkManager-libreswan), where it fails to properly sanitize the VPN configuration from the local unprivileged user. In this configuration, composed by a key-value format, the plugin fails to escape special characters, leading the application to interpret values as keys. One of the most critical parameters that could be abused by a malicious user is the `leftupdown`key. This key takes an executable command as a value and is used to specify what executes as a callback in NetworkManager-libreswan to retrieve configuration settings back to NetworkManager. As NetworkManager uses Polkit to allow an unprivileged user to control the system's network configuration, a malicious actor could achieve local privilege escalation and potential code execution as root in the targeted machine by creating a malicious configuration.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- NetworkManager-libreswan
fixed in 1.2.24
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported
- NetworkManager-libreswan
Version range not reported