CVE-2009-4144: Medium severity red hat networkmanager-libreswan-gnome vulnerability
+++ This bug was initially created as a clone of Bug #546793 +++
See also:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560067
If the user had set up a WPA Enterprise or 802.1x connection that used a CA certificate to verify the identity of the network to which the user was connecting, and the user deleted or moved that CA certificate file at a later point, NetworkManager will still connect to that network but without using the CA certificate. This could result in connections to a rogue network that is spoofing the original network as the identity of the network is not verified with the CA certificate after the certificate has been deleted.
Obviously requires direct interaction by the user that configured the connection in the first place to remove the CA certificate file.
--- Additional comment from dcbw on 2009-12-11 18:50:57 EDT ---
Upstream fix is:
http://git.gnome.org/cgit/network-manager-applet/commit/?h=NETWORKMANAGERAPPLET07&id=4020594dfbf566f1852f0acb36ad631a9e73a82b
Other sources
NetworkManager (NM) 0.7.2 does not ensure that the configured Certification Authority (CA) certificate file for a (1) WPA Enterprise or (2) 802.1x network remains present upon a connection attempt, which might allow remote attackers to obtain sensitive information or cause a denial of service (connectivity disruption) by spoofing the identity of a wireless network.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2009-4144?
CVE-2009-4144 is classified as a low-severity vulnerability affecting NetworkManager versions 0.7.2.
How do I fix CVE-2009-4144?
To fix CVE-2009-4144, update NetworkManager to a version that includes the relevant security patches beyond 0.7.2.
What systems are impacted by CVE-2009-4144?
CVE-2009-4144 specifically affects systems running NetworkManager version 0.7.2.
What type of vulnerability is CVE-2009-4144?
CVE-2009-4144 is a bug that may lead to unexpected behavior in NetworkManager.
Is there a workaround for CVE-2009-4144?
There is no officially recommended workaround for CVE-2009-4144 other than upgrading the affected software.