Skip to content
VulniPulse
Advisory severityHigh7.8Red Hat Linux

High [CVE-2024-9050] Networkmanager-libreswan: local privilege escalation via leftupdown

This high-severity Red Hat Linux advisory covers CVE-2024-9050 affecting Red Hat Enterprise Linux 7.7 Advanced Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8.2 Advanced Update Support.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2024-9050 Source published Source updated

VulniPulse record published

CVE-2024-9050
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

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.

This issue marked with an Important severity due to its potential to enable local privilege escalation and arbitrary code execution. Since NetworkManager uses Polkit to allow unprivileged users to manage network configurations, the failure to properly sanitize the VPN configuration, particularly the `leftupdown` key, creates a direct attack vector.

Is CVE-2024-9050 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2024-9050 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2024-9050?

Upgrade to a fixed release named by Red Hat:

  • NetworkManager-libreswan-0:1.2.4-4.el7_7
  • NetworkManager-libreswan-0:1.2.4-4.el7_9
  • NetworkManager-libreswan-0:1.2.10-7.el8_10
  • NetworkManager-libreswan-0:1.2.10-6.el8_2
  • NetworkManager-libreswan-0:1.2.10-6.el8_4
  • NetworkManager-libreswan-0:1.2.10-6.el8_6
  • NetworkManager-libreswan-0:1.2.10-6.el8_8
  • NetworkManager-libreswan-0:1.2.22-4.el9_5
  • NetworkManager-libreswan-0:1.2.14-3.el9_0
  • NetworkManager-libreswan-0:1.2.14-6.el9_2
  • NetworkManager-libreswan-0:1.2.18-6.el9_4
  • RHSA-2024:8338

10 more fixed releases are listed below.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Fixed versions
  • NetworkManager-libreswan-0:1.2.4-4.el7_7
  • NetworkManager-libreswan-0:1.2.4-4.el7_9
  • NetworkManager-libreswan-0:1.2.10-7.el8_10
  • NetworkManager-libreswan-0:1.2.10-6.el8_2
  • NetworkManager-libreswan-0:1.2.10-6.el8_4
  • NetworkManager-libreswan-0:1.2.10-6.el8_6
  • NetworkManager-libreswan-0:1.2.10-6.el8_8
  • NetworkManager-libreswan-0:1.2.22-4.el9_5
  • NetworkManager-libreswan-0:1.2.14-3.el9_0
  • NetworkManager-libreswan-0:1.2.14-6.el9_2
  • NetworkManager-libreswan-0:1.2.18-6.el9_4
  • RHSA-2024:8338
  • RHSA-2024:8357
  • RHSA-2024:8353
  • RHSA-2024:8358
  • RHSA-2024:8355
  • RHSA-2024:8356
  • RHSA-2024:8354
  • RHSA-2024:9555
  • RHSA-2024:8312
  • RHSA-2024:8352
  • RHSA-2024:9556

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • A mitigation for this issue is either unavailable or the existing options do not meet Red Hat Product Security's standards for ease of use, deployment, widespread applicability, or stability. One potential approach is to prevent local users from controlling networking through polkit. However, this would also block them from connecting to new Wi-Fi networks, which is not ideal for laptops but might be acceptable for workstations. Server customers typically don't need to be concerned, as they generally don't have local users capable of exploiting the bug.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Get an email when Red Hat RHEL & SELinux publishes the next one.

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat RHEL & SELinux
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.