LiveActive security incident?Get immediate response
CVE Record

CVE-2020-6096: An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.3...

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-impact glibc flaw affecting ARMv7 systems using the vulnerable GNU memcpy implementation. If software passes an attacker-influenced length that underflows, memory can be corrupted instead of failing safely. Business urgency depends on whether ARMv7 Linux assets run affected glibc builds and expose code paths that copy untrusted data.

Executive priority

Treat as high priority for ARMv7 fleets, especially embedded or externally reachable systems. It is not a broad all-platform glibc emergency based on the supplied evidence, but vulnerable ARMv7 deployments could face severe confidentiality, integrity, and availability impact.

Technical view

CVE-2020-6096 is a CWE-195 signed comparison issue in ARMv7 memcpy in GNU glibc 2.30.9000. A negative or underflowed num value can lead to undefined behavior, out-of-bounds memory writes, continued execution with corrupted data, and potential remote code execution. CVSS is 8.1 with network attack vector and high complexity.

Likely exposure

Most relevant exposure is ARMv7 Linux systems, embedded devices, appliances, or containers using vulnerable glibc builds. Non-ARMv7 systems are not indicated by the provided sources. Actual exposure requires confirming distro backports and whether applications pass attacker-controlled sizes into memcpy-reachable paths.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Talos and the CVE description characterize the bug as exploitable and potentially remotely reachable, but exploitation is high complexity and application-context dependent.

Researcher notes

Focus analysis on ARMv7 glibc memcpy behavior and downstream distro patch status. The provided evidence names GNU glibc 2.30.9000 and advisory coverage, but does not enumerate every affected downstream version, patch level, or real-world exploitation case.

Mitigation direction

  • Apply vendor glibc updates for affected ARMv7 systems.
  • Use distro advisories from Fedora, Gentoo, Debian, or the relevant vendor.
  • Rebuild or restart services using the updated glibc package.
  • Prioritize internet-facing or untrusted-input ARMv7 workloads.
  • Check vendor guidance if running non-distro or embedded glibc builds.

Validation and detection

  • Inventory ARMv7 assets and installed glibc versions.
  • Confirm whether vendor packages include CVE-2020-6096 fixes or backports.
  • Identify applications processing untrusted input on affected systems.
  • Verify patched glibc is loaded after service restart or reboot.
  • Track exceptions for unsupported embedded firmware or static builds.
Prepared
Confidence
high
Sources
8

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-195: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-6096 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
8.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/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
8Source 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
8.1CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.1High
CVSS 3.0 vector shape for CVE-2020-6096Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aGNU glibc2.30.9000Listed
Weakness

CWE details

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

CWE-195 · source CWE mapping

Signed to Unsigned Conversion Error

Signed to Unsigned Conversion Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.