Security readout for executives and security teams
Plain-English summary
CVE-2021-0474 is an Android memory corruption flaw that could allow remote code execution without user interaction or extra privileges. The source does not provide CVSS scoring, but the stated impact is serious because affected devices may be compromised remotely if unpatched.
Executive priority
Treat this as high priority for Android fleets because the stated impact is remote code execution without user interaction. The main business action is patch verification and removal of unsupported devices.
Technical view
The flaw is an out-of-bounds write caused by a heap buffer overflow in avrc_msg_cback within avrc_api.cc. The CVE record lists Android 8.1, 9, 10, and 11 as affected and identifies Android issue A-177611958.
Likely exposure
Exposure is limited to Android 8.1, 9, 10, and 11 devices that have not received the applicable Android security bulletin fixes from their vendor or device OEM.
Exploitation context
The source states exploitation needs no user interaction and no additional privileges. It does not cite active exploitation, and the CVE is not listed as KEV in the supplied bundle.
Researcher notes
Public details in the supplied bundle are sparse: no CVSS vector, CWE, proof-of-concept status, or detailed patch note is provided. Analysis should stay anchored to Android issue A-177611958 and the May 2021 bulletin.
Mitigation direction
- Review the Android Security Bulletin dated 2021-05-01 for vendor guidance.
- Apply applicable Android or OEM security updates to affected devices.
- Prioritize unmanaged, legacy, or rarely updated Android endpoints.
- Retire devices that cannot receive relevant security updates.
Validation and detection
- Inventory Android devices running versions 8.1, 9, 10, or 11.
- Confirm each device has received the relevant May 2021 Android security update or later OEM patch.
- Check MDM or endpoint records for stale Android patch levels.
- Document unsupported devices and remove them from sensitive environments.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
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 lookupCVE-2021-0474 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/2021-05-01CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.