BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-0213High confidence

In hevcd_fmt_conv_420sp_to_420sp_av8 of ihevcd_fmt_conv_420sp_to_420sp.s, there is a possible out of bounds write due to a heap buffer overflow

Unknown · Android

6.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.86% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Android and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2020-1717

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In hevcd_fmt_conv_420sp_to_420sp_av8 of ihevcd_fmt_conv_420sp_to_420sp.s, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-10 Android-11 Android ID: A-143464314

What

In hevcd_fmt_conv_420sp_to_420sp_av8 of ihevcd_fmt_conv_420sp_to_420sp.s, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-10 Android-11 Android ID: A-143464314

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

In hevcd_fmt_conv_420sp_to_420sp_av8 of ihevcd_fmt_conv_420sp_to_420sp.s, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android Versions: Android-10 Android-11 Android ID: A-143464314

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Write → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20200617Security Bulletin 17 Jun 2020

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 17 Jun 2020, published on 17 June 2020. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-619Multiples vulnérabilités dans Google Android

Android toutes versions sans le correctif de sécurité du 05 octobre 2020 Résumé De multiples vulnérabilités ont été découvertes dans Google Android. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, une atteinte à la confidentialité des données et une élévation de privilèges. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Android du 05 octobre 2020 https://source.android.com/security/bulletin/2020-10-01 Référence CVE CVE-2019-2194 https://www.cve.org/CVERecord?id=CVE-2019-2194 Référence CVE CVE-2020-0213 https://www.cve.org/CVERecord?id=CVE-2020-0213 Référence CVE CVE-2020-0215 https://www.cve.org/CVERecord?id=CVE-2020-0215 Référence CVE CVE-2020-0246 https://www.cve.org/CVERecord?id=CVE-2020-0246 Référence CVE CVE-2020-0283 https://www.cve.org/CVERecord?id=CVE-2020-0283 Référence CVE CVE-2020-0339 https://www.cve.org/CVERecord?id=CVE-2020-0339 Référence CVE CVE-2020-0367 https://www.cve.org/CVERecord?id=CVE-2020-0367 Référence CVE CVE-2020-0371 https://www.cve.org/CVERecord?id=CVE-2020-0371 Référence CVE CVE-2020-0376 https://www.cve.org/CVERecord?id=CVE-2020-0376 Référence CVE CVE-2020-0377 https://www.cve.org/CVERecord?id=CVE-2020-0377 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-331Multiples vulnérabilités dans Google Android

.cve.org/CVERecord?id=CVE-2020-0204 Référence CVE CVE-2020-0205 https://www.cve.org/CVERecord?id=CVE-2020-0205 Référence CVE CVE-2020-0206 https://www.cve.org/CVERecord?id=CVE-2020-0206 Référence CVE CVE-2020-0207 https://www.cve.org/CVERecord?id=CVE-2020-0207 Référence CVE CVE-2020-0208 https://www.cve.org/CVERecord?id=CVE-2020-0208 Référence CVE CVE-2020-0209 https://www.cve.org/CVERecord?id=CVE-2020-0209 Référence CVE CVE-2020-0210 https://www.cve.org/CVERecord?id=CVE-2020-0210 Référence CVE CVE-2020-0211 https://www.cve.org/CVERecord?id=CVE-2020-0211 Référence CVE CVE-2020-0212 https://www.cve.org/CVERecord?id=CVE-2020-0212 Référence CVE CVE-2020-0213 https://www.cve.org/CVERecord?id=CVE-2020-0213 Référence CVE CVE-2020-0214 https://www.cve.org/CVERecord?id=CVE-2020-0214 Référence CVE CVE-2020-0215 https://www.cve.org/CVERecord?id=CVE-2020-0215 Référence CVE CVE-2020-0216 https://www.cve.org/CVERecord?id=CVE-2020-0216 Référence CVE CVE-2020-0217 https://www.cve.org/CVERecord?id=CVE-2020-0217 Référence CVE CVE-2020-0218 https://www.cve.org/CVERecord?id=CVE-2020-0218 Référence CVE CVE-2020-0219 https://www.cve.org/CVERecord?id=CVE-2020-0219 Référence CVE CVE-2020-0223 https://www.cve.org/CVERecord?id=CVE-2020-0223 Référence CVE CVE-2020-0232 https://www.cve.org/CVERecord?id=CVE-2020-0232 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-006463Android における境界外書き込みに関する脆弱性

Android には、境界外書き込みに関する脆弱性が存在します。 本脆弱性は、Android ID: A-143464314 として公開されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Android: Android-10
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jun 2020 · Last source change 4 Aug 2024, 05:55 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2020-1717
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-0213 · cve.blacktree.nl