Networkmanager-libreswan: local privilege escalation via leftupdown
Published Oct 22, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Networkmanager-libreswan: local privilege escalation via leftupdown
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2024:8312 ↗
- RHSA-2024:8338 ↗
- RHSA-2024:8352 ↗
- RHSA-2024:8353 ↗
- RHSA-2024:8354 ↗
- RHSA-2024:8355 ↗
- RHSA-2024:8356 ↗
- RHSA-2024:8357 ↗
- RHSA-2024:8358 ↗
- RHSA-2024:9555 ↗
- RHSA-2024:9556 ↗
- access.redhat.com ↗
Record history
Published Oct 22, 2024 · Last refreshed Nov 3, 2026