CVE-2022-20130
Published: 15 June 2022
Summary
CVE-2022-20130 is a critical-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Google Android. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 5.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
In transportDec_OutOfBandConfig within tpdec_lib.cpp, a heap buffer overflow permits an out-of-bounds write on Android 10, 11, 12, and 12L. The flaw carries a CVSS score of 9.8 and is tracked under Android ID A-224314979 and CWE-754.
Remote attackers can trigger the issue over the network with no privileges or user interaction required, resulting in remote code execution. The June 2022 Android security bulletin lists the vulnerability among the issues resolved in the corresponding monthly patch release.
EPSS for the CVE reached a peak of 0.2391 and stands at 0.1609 currently.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-25390
Vulnerability details
In transportDec_OutOfBandConfig of tpdec_lib.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10…
more
Android-11 Android-12 Android-12LAndroid ID: A-224314979
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires detection and response to audit logging failures as an unusual or exceptional condition.
Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions.
Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations.
IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents.
Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions.
Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves.
Requires detection of unusual conditions followed by a controlled transition to the defined failure state.
MTTF determination forces explicit checks for conditions that precede predictable component failure.