Skip to content
Fencer Intel
medium 5.5

CVE-2021-20297 json

A flaw was found in NetworkManager in versions before 1.30.0.

published 5y ago modified 4mo ago also EUVD-2021-7722

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

A flaw was found in NetworkManager in versions before 1.30.0. Setting match.path and activating a profile crashes NetworkManager. The highest threat from this vulnerability is to system availability.

Patch / fix

  • gnome networkmanager 1.30.0
  • network-manager Debian 14, Debian 13, Debian 12 1.30.0-2

debian advisories DEBIAN-CVE-2021-20297

  • libnma RHEL 8 1.8.30-2.el8
  • NetworkManager RHEL 8 1:1.30.0-7.el8
  • NetworkManager-ovs RHEL 8 1:1.30.0-7.el8
  • NetworkManager-ppp RHEL 8 1:1.30.0-7.el8
  • NetworkManager-tui RHEL 8 1:1.30.0-7.el8
  • NetworkManager-adsl RHEL 8 1:1.30.0-7.el8
  • NetworkManager-team RHEL 8 1:1.30.0-7.el8
  • NetworkManager-wifi RHEL 8 1:1.30.0-7.el8

red hat advisories RHSA-2021:1574

  • NetworkManager openSUSE Tumbleweed 1.32.10-2.1

opensuse advisories openSUSE-SU-2024:10602-1

  • libnma Rocky Linux 8 1.8.30-2.el8
  • NetworkManager Rocky Linux 8 1:1.30.0-7.el8

rocky linux advisories RLSA-2021:1574

  • networkmanager Alpine 3.13 1.26.6-r1
  • networkmanager-elogind Alpine 3.13 1.26.6-r1

alpine advisories ALPINE-CVE-2021-20297

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • networkmanager Arch Linux 1.30.4-1

arch linux advisories AVG-1759

Is CVE-2021-20297 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2021-20297 updated cvss 5.5

NetworkManager: Profile with match.path setting triggers crash

  • Red Hat OpenShift Container Platform 4 NetworkManager, NetworkManager-ovs, NetworkManager-ppp, NetworkManager-tui, NetworkManager-adsl, NetworkManager-team, +9 more
    affected: no fix planned “Will not fix”
  • Red Hat CodeReady Linux Builder (v. 8) libnma-devel 1.8.30-2.el8, libnma-debuginfo 1.8.30-2.el8, libnma-debugsource 1.8.30-2.el8, NetworkManager-debuginfo 1.30.0-7.el8, NetworkManager-debugsource 1.30.0-7.el8, NetworkManager-libnm-devel 1.30.0-7.el8, +10 more Red Hat Enterprise Linux AppStream (v. 8) libnma 1.8.30-2.el8, NetworkManager-cloud-setup 1.30.0-7.el8 Red Hat Enterprise Linux BaseOS (v. 8) NetworkManager 1.30.0-7.el8, NetworkManager-ovs 1.30.0-7.el8, NetworkManager-ppp 1.30.0-7.el8, NetworkManager-tui 1.30.0-7.el8, NetworkManager-adsl 1.30.0-7.el8, NetworkManager-team 1.30.0-7.el8, +7 more
    fixed: vendor fix RHSA-2021:1574
  • Red Hat Enterprise Linux 6 NetworkManager, NetworkManager-glib, NetworkManager-gnome Red Hat Enterprise Linux 7 NetworkManager, NetworkManager-ovs, NetworkManager-ppp, NetworkManager-tui, NetworkManager-adsl, NetworkManager-glib, +8 more Red Hat Enterprise Linux 9 NetworkManager, NetworkManager-ovs, NetworkManager-ppp, NetworkManager-tui, NetworkManager-adsl, NetworkManager-team, +9 more
    not affected: vulnerable code not present

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

Exploit prediction

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

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:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • n/a NetworkManager

Classification

Weakness
  • CWE-20 Improper Input 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.