VYPR
Unrated severityNVD Advisory· Published Dec 26, 2019· Updated Aug 6, 2024

CVE-2012-2736

CVE-2012-2736

Description

NetworkManager 0.9.2.0 creates an open AdHoc network when users attempt to create a WPA/WPA2-secured AdHoc wireless network.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

NetworkManager 0.9.2.0 creates an open AdHoc network when users attempt to create a WPA/WPA2-secured AdHoc wireless network.

Vulnerability

In NetworkManager version 0.9.2.0, when a user attempts to create a new wireless network with WPA/WPA2 security in AdHoc mode, the resulting network is created as an open, insecure network due to incorrect handling by certain wireless drivers [1][2][3]. The bug affects both NetworkManager and the network-manager-applet [4].

Exploitation

An attacker must be within wireless range of a user who creates a WPA-secured AdHoc network. No prior authentication or special privileges are needed; the user's action alone triggers the creation of an open network. The attacker can then connect to the network without providing any credentials [2][3].

Impact

Successful exploitation allows the attacker to gain unauthorized access to the wireless network, enabling eavesdropping on communications and potential data injection. Both confidentiality and integrity of network traffic are compromised [1][2].

Mitigation

The vulnerability is addressed by updating NetworkManager to a version that completely disables the option to create WPA-secured AdHoc connections. Ubuntu released USN-1483-2 for network-manager-applet [4]. Red Hat marked the issue as WONTFIX (low priority) [3]. Users should apply the available updates or avoid creating WPA-secured AdHoc networks.

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

8

News mentions

0

No linked articles in our index yet.