LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22429: redox-os v0.1.0 was discovered to contain a use-after-free bug via the gethostbyaddr() function at /src/hea...

redox-os v0.1.0 was discovered to contain a use-after-free bug via the gethostbyaddr() function at /src/header/netdb/mod.rs.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-22429 is a use-after-free memory bug reported in Redox OS relibc v0.1.0. If exploitable in a deployed system, it could affect confidentiality, integrity, and availability. The public metadata does not identify broad enterprise products, CPEs, a patch version, or active exploitation.

Executive priority

Treat as high priority only where Redox OS relibc is used. For most organizations, urgency is likely low unless Redox appears in products, labs, embedded work, or custom builds.

Technical view

The issue is CWE-416 in gethostbyaddr() at /src/header/netdb/mod.rs, with CVSS 3.1 score 7.8. The vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to environments using Redox OS relibc v0.1.0 or software built against the vulnerable relibc code. The CVE affected-product metadata is incomplete, listing vendor, product, versions, and CPEs as n/a.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates local access with low privileges is required, so this is not described as a remote unauthenticated internet-facing issue.

Researcher notes

Key gaps are incomplete affected-product metadata, no CPEs, no named fixed version, and no active exploitation evidence in the bundle. Analysis should stay tied to Redox OS relibc v0.1.0 and the referenced gethostbyaddr() memory safety defect.

Mitigation direction

  • Inventory any Redox OS or relibc usage in deployed, test, and research systems.
  • Check the Redox GitLab issue and upstream guidance for fixed versions or commits.
  • Update or rebuild affected relibc components when an upstream fix is identified.
  • Limit local untrusted user access on systems confirmed to use affected code.
  • Document acceptance if Redox OS relibc is not present in the environment.

Validation and detection

  • Confirm whether Redox OS relibc v0.1.0 exists in assets or build dependencies.
  • Review dependency manifests, images, and source checkouts for relibc references.
  • Verify whether gethostbyaddr() from the affected code path is present.
  • Record upstream issue status and any available remediation evidence.
  • Confirm compensating controls for local user access where affected systems remain.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-22429 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-22429Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-416

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs