CVE-2011-2176: GNOME NetworkManager before 0.8.6 does not properly enforce the auth_admin element in PolicyKit, which allows local users to bypass intended…
Noroxi assessment
Priority: Monitor (action score 8/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: network-manager (Debian:12) 0.9.0-1; NetworkManager (Red Hat:enterprise_linux:6::server) 1:0.8.1-9.el6_1.1; NetworkManager-debuginfo (Red Hat:enterprise_linux:6::server) 1:0.8.1-9.el6_1.1.
Low priority for now. Upgrade to network-manager (Debian:12) 0.9.0-1; NetworkManager (Red Hat:enterprise_linux:6::server) 1:0.8.1-9.el6_1.1; NetworkManager-debuginfo (Red Hat:enterprise_linux:6::server) 1:0.8.1-9.el6_1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
GNOME NetworkManager before 0.8.6 does not properly enforce the auth_admin element in PolicyKit, which allows local users to bypass intended wireless network sharing restrictions via unspecified vectors.
- Published
- Sep 2, 2011
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-287
Report tools
Action score
8
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnome | networkmanager | cpe:2.3:a:gnome:networkmanager |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnome networkmanagerup to 0.8.4 inclusive
- gnome networkmanager0.2.0
- gnome networkmanager0.3.0
- gnome networkmanager0.3.1
- gnome networkmanager0.4.1
- gnome networkmanager0.5.0
- gnome networkmanager0.5.1
- gnome networkmanager0.6.0
+8 more rows
- gnome networkmanager0.6.1
- gnome networkmanager0.6.2
- gnome networkmanager0.6.6
- gnome networkmanager0.7.0
- gnome networkmanager0.7.1
- gnome networkmanager0.7.2
- gnome networkmanager0.8.1
- gnome networkmanager0.8.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | network-manager | before 0.9.0-1 | 0.9.0-1 |
| Red Hat:enterprise_linux:6::server | NetworkManager | before 1:0.8.1-9.el6_1.1 | 1:0.8.1-9.el6_1.1 |
| Red Hat:enterprise_linux:6::server | NetworkManager-debuginfo | before 1:0.8.1-9.el6_1.1 | 1:0.8.1-9.el6_1.1 |
| Red Hat:enterprise_linux:6::server | NetworkManager-devel | before 1:0.8.1-9.el6_1.1 | 1:0.8.1-9.el6_1.1 |
| Red Hat:enterprise_linux:6::server | NetworkManager-glib | before 1:0.8.1-9.el6_1.1 | 1:0.8.1-9.el6_1.1 |
| Red Hat:enterprise_linux:6::server | NetworkManager-glib-devel | before 1:0.8.1-9.el6_1.1 | 1:0.8.1-9.el6_1.1 |
| Red Hat:enterprise_linux:6::server | NetworkManager-gnome | before 1:0.8.1-9.el6_1.1 | 1:0.8.1-9.el6_1.1 |
Same product
gnome: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1000135GNOME NetworkManager version 1.10.2 and earlier contains a Information Exposure (CWE-200) vulnerability in DNS resolver that can result in…31Monitor
- CVE-2005-2410Format string vulnerability in the nm_info_handler function in Network Manager may allow remote attackers to execute arbitrary code via…31Monitor
- CVE-2009-4144NetworkManager (NM) 0.7.2 does not ensure that the configured Certification Authority (CA) certificate file for a (1) WPA Enterprise or (2)…28Monitor
Published before and after this one in the same product
- ← EarlierCVE-2009-4145Dec 23, 2009 · nm-connection-editor in NetworkManager (NM) 0.7.x exports connection objects over D-Bus upon actions in the connection editor GUI, which…8Monitor
- ← EarlierCVE-2011-1943Jun 14, 2011 · The destroy_one_secret function in nm-setting-vpn.c in libnm-util in the NetworkManager package 0.8.999-3.git20110526 in Fedora 15 creates…8Monitor
- Later →CVE-2015-0272Nov 17, 2015 · GNOME NetworkManager allows remote attackers to cause a denial of service (IPv6 traffic disruption) via a crafted MTU value in an IPv6…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:network-manager | 0.9.0-1 · Debian:12 | Package registry (OSV) |
| red hat:NetworkManager | 1:0.8.1-9.el6_1.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:NetworkManager-debuginfo | 1:0.8.1-9.el6_1.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:NetworkManager-devel | 1:0.8.1-9.el6_1.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:NetworkManager-glib | 1:0.8.1-9.el6_1.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:NetworkManager-glib-devel | 1:0.8.1-9.el6_1.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:NetworkManager-gnome | 1:0.8.1-9.el6_1.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:L/AC:L/Au:N/C:N/I:P/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.