LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0557: In setRange of ABuffer.cpp, there is a possible out of bounds write due to an integer overflow.

In setRange of ABuffer.cpp, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-179046129

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-0557 is an Android 11 memory corruption issue that could allow remote code execution after user interaction. The provided sources do not report active exploitation. Business urgency depends mainly on whether Android 11 devices remain unpatched from the June 2021 Android/Pixel security update timeframe.

Executive priority

Prioritize remediation for any remaining Android 11 fleet. This is a potential remote code execution issue, but the age of the bulletin, user-interaction requirement, and lack of KEV evidence make patch verification the practical priority rather than emergency response.

Technical view

The CVE describes an integer overflow in setRange of ABuffer.cpp leading to a possible out-of-bounds write. The stated impact is remote code execution with no additional execution privileges, but exploitation requires user interaction. No CVSS score, CWE mapping, or exploit details are provided in the source bundle.

Likely exposure

Exposure is most likely on Android 11 devices that did not receive the relevant June 2021 security fixes from Google, Pixel, OEM, or carrier update channels. Patched devices and devices no longer running affected Android 11 builds are less likely exposed.

Exploitation context

The sources state user interaction is needed and no additional execution privileges are required. The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization, so active exploitation should not be assumed.

Researcher notes

Key missing evidence includes CVSS, CWE, exact reachable attack surface, exploit maturity, and detailed fix information. Treat the provided Android description as authoritative for impact, but avoid assuming affected components, media formats, or exploitation paths beyond ABuffer.cpp setRange.

Mitigation direction

  • Apply the relevant June 2021 Android or Pixel security update where available.
  • Check OEM and carrier advisories for affected Android 11 device models.
  • Retire or isolate Android 11 devices that can no longer receive security updates.
  • Use MDM policy to enforce minimum Android security patch levels.

Validation and detection

  • Inventory Android 11 devices across managed and unmanaged fleets.
  • Verify each device security patch level is June 2021 or later, where applicable.
  • Confirm OEM bulletins map the fix to each deployed model.
  • Review MDM compliance reports for devices below the approved patch level.
Prepared
Confidence
medium
Sources
3

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.

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-2021-0557 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
2Source 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/aAndroidAndroid-11Listed
Weakness

CWE details

No CWE listed

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