Skip to content
Fencer Intel
medium 5.5

CVE-2012-1096 json

NetworkManager 0.9 and earlier allows local users to use other users' certificates or private keys when making a connection via the file pa…

published 2020-03-10 6 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1132

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
1
Exploit-DB

Summary

NetworkManager 0.9 and earlier allows local users to use other users' certificates or private keys when making a connection via the file path when adding a new connection.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-1096 updated cvss 4.7

wpa_supplicant: Improper x509v3 certificate and key file paths sanitization

  • Red Hat Enterprise Linux 4 NetworkManager, wpa_supplicant Red Hat Enterprise Linux 5 NetworkManager, wpa_supplicant Red Hat Enterprise Linux 6 NetworkManager, wpa_supplicant, NetworkManager-glib, NetworkManager-gnome
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-36887)
  2. Published

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-36887 GNOME NetworkManager 0.x - Local Arbitrary File Access local, 2012-02-29

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:C/I:N/A:N

Affected products

  • GNOME NetworkManager

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.