CVE-2020-10754: It was found that nmcli, a command line interface to NetworkManager did not honour 802-1x.ca-path and 802-1x.phase2-ca-path settings, when c
Noroxi assessment
Priority: Monitor (action score 17/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.99% (FIRST EPSS); higher than 62.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: network-manager (Debian:12) 1.24.2-1; NetworkManager (openSUSE:Tumbleweed) 1.32.10-2.1; NetworkManager (Red Hat:enterprise_linux:7::client) 1:1.18.8-1.el7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to network-manager (Debian:12) 1.24.2-1; NetworkManager (openSUSE:Tumbleweed) 1.32.10-2.1; NetworkManager (Red Hat:enterprise_linux:7::client) 1:1.18.8-1.el7 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
It was found that nmcli, a command line interface to NetworkManager did not honour 802-1x.ca-path and 802-1x.phase2-ca-path settings, when creating a new profile. When a user connects to a network using this profile, the authentication does not happen and the connection is made insecurely.
- Published
- Jun 8, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-287
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CNA vs NVD score
- NVD
- 4.3
- CNA · redhat
- 4.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora31
- gnome networkmanagerbefore 1.22.14
- gnome networkmanager1.24.0 and later · before 1.24.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
[Red Hat] NetworkManager
- 1.24.2affected
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 1.24.2-1 | 1.24.2-1 |
| openSUSE:Tumbleweed | NetworkManager | before 1.32.10-2.1 | 1.32.10-2.1 |
| Red Hat:enterprise_linux:7::client | NetworkManager | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-adsl | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-bluetooth | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-debuginfo | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-dispatcher-routing-rules | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-glib | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-glib-devel | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-libnm | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-libnm-devel | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-ovs | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-ppp | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-team | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-tui | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-wifi | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::client | NetworkManager-wwan | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:7::server | NetworkManager-config-server | before 1:1.18.8-1.el7 | 1:1.18.8-1.el7 |
| Red Hat:enterprise_linux:8::appstream | NetworkManager-adsl-debuginfo | before 1:1.22.8-5.el8_2 | 1:1.22.8-5.el8_2 |
| Red Hat:enterprise_linux:8::appstream | NetworkManager-bluetooth-debuginfo | before 1:1.22.8-5.el8_2 | 1:1.22.8-5.el8_2 |
| Red Hat:enterprise_linux:8::appstream | NetworkManager-cloud-setup | before 1:1.22.8-5.el8_2 | 1:1.22.8-5.el8_2 |
| Red Hat:enterprise_linux:8::appstream | NetworkManager-cloud-setup-debuginfo | before 1:1.22.8-5.el8_2 | 1:1.22.8-5.el8_2 |
| Red Hat:enterprise_linux:8::appstream | NetworkManager-debuginfo | before 1:1.22.8-5.el8_2 | 1:1.22.8-5.el8_2 |
| Red Hat:enterprise_linux:8::appstream | NetworkManager-debugsource | before 1:1.22.8-5.el8_2 | 1:1.22.8-5.el8_2 |
+21
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 P31Monitor
- CVE-2005-2410Format string vulnerability in the nm_info_handler function in Network Manager may allow remote attackers to execute arbitrary code via form31Monitor
- 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-2006-7246Jan 27, 2020 · NetworkManager 0.9.x does not pin a certificate's subject to an ESSID when 802.11X authentication is used.27Monitor
- ← EarlierCVE-2012-1096Mar 10, 2020 · NetworkManager 0.9 and earlier allows local users to use other users' certificates or private keys when making a connection via the file pat22Monitor
- Later →CVE-2021-20297May 26, 2021 · A flaw was found in NetworkManager in versions before 1.30.0.22Monitor
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 | 1.24.2-1 · Debian:12 | Package registry (OSV) |
| opensuse:NetworkManager | 1.32.10-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:NetworkManager-adsl-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-bluetooth-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-cloud-setup | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-cloud-setup-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-debugsource | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-libnm-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-ovs-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-ppp-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-team-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-tui-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:NetworkManager-wifi-debuginfo | 1:1.22.8-5.el8_2 · Red Hat:enterprise_linux:8::appstream | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0448 · Jun 7, 2021(IBM Güvenlik Bülteni Yayınladı)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.