LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20795: iproute2 before 5.1.0 has a use-after-free in get_netnsid_from_name in ip/ipnetns.c.

iproute2 before 5.1.0 has a use-after-free in get_netnsid_from_name in ip/ipnetns.c. NOTE: security relevance may be limited to certain uses of setuid that, although not a default, are sometimes a configuration option offered to end users. Even when setuid is used, other factors (such as C library configuration) may block exploitability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2019-20795 is a memory safety bug in iproute2 before 5.1.0. The public record says security impact may be limited because exploitability depends on unusual setuid configurations and other system factors. Treat it as a hygiene and hardening issue unless your environment intentionally exposes iproute2 with elevated privileges.

Executive priority

Prioritize remediation during normal Linux patch cycles, and accelerate only for systems where iproute2 is granted elevated execution. The available evidence does not support emergency response for default configurations, but outdated privileged tooling should be cleaned up promptly.

Technical view

The flaw is a use-after-free in get_netnsid_from_name in ip/ipnetns.c. Sources identify iproute2 before 5.1.0 as affected. The CVE record does not provide CVSS, CWE, exploit details, or universal exploitability; it specifically cautions that setuid and libc behavior affect security relevance.

Likely exposure

Linux systems with iproute2 before 5.1.0 may carry the vulnerable code. Practical exposure is most concerning where iproute2 tools are configured setuid or otherwise reachable with elevated privileges, which the CVE notes is not a default configuration.

Exploitation context

No source in the bundle reports active exploitation, and the CVE is not listed as KEV. Public evidence describes constrained exploitability rather than a broadly weaponized condition. Researchers should avoid assuming exploitability without confirming local setuid and library conditions.

Researcher notes

Focus validation on privilege context, not just package presence. The CVE’s own note narrows relevance to certain setuid uses and mentions library behavior as a possible blocker. Source data is sparse, so avoid claiming reliable exploitation paths from this bundle alone.

Mitigation direction

  • Upgrade iproute2 using the relevant Linux distribution advisory or package channel.
  • Confirm the installed package includes the upstream fix for versions before 5.1.0.
  • Remove setuid exposure from iproute2 tools unless explicitly required.
  • Review Ubuntu, Gentoo, SUSE, or other vendor guidance for backported fixes.

Validation and detection

  • Inventory hosts running iproute2 versions older than 5.1.0 or vendor-flagged builds.
  • Check whether iproute2 or ip tools are configured with setuid privileges.
  • Confirm vendor security updates for iproute2 are installed on affected distributions.
  • Document any systems intentionally relying on elevated iproute2 execution.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-20795 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.