NetworkManager-l2tp: local privilege escalation via ipsec.conf injection
- 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.0.16, 1.2.22, 1.8.10, 1.20.24, 1.52.4
- 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 NetworkManager-l2tp. The plugin writes attacker-controlled VPN connection properties (vpn.data and vpn.secrets values) unescaped into a generated ipsec.conf file that pluto loads as root. A local unprivileged user can create and activate their own L2TP VPN profile containing a newline-injected leftupdown directive; pluto executes that command as root when the IKE security association is established, resulting in local privilege escalation. This is the same bug class as CVE-2018-10900 (NetworkManager-vpnc).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- NetworkManager-l2tp
From 1.0.0 · fixed in 1.0.16; From 1.2.0 · fixed in 1.2.22; From 1.8.0 · fixed in 1.8.10; From 1.20.0 · fixed in 1.20.24; From 1.52.0 · fixed in 1.52.4
- NetworkManager-l2tp
From 1.52.0 · fixed in 1.52.4
- NetworkManager-l2tp
From 1.20.0 · fixed in 1.20.24