Security Resilience

CVE-2023-35680

Google Android 11.0 … 13.0

Published
11 September 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0012 2th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-35680 is a medium-severity Unsafe Reflection (CWE-470) vulnerability in Google Android. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

In multiple locations, there is a possible way to import contacts belonging to other users due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CWE(s)
NVD-CWE-OtherCWE-470

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
attack.mitre.org →
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
attack.mitre.org →
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
attack.mitre.org →
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-21390Same product: Google Android
CVE-2024-23705Same product: Google Android
CVE-2026-0127Same product: Google Android
CVE-2023-48397Same product: Google Android
CVE-2026-0165Same product: Google Android
CVE-2026-0094Same product: Google Android
CVE-2025-48636Same product: Google Android
CVE-2025-48577Same product: Google Android
CVE-2024-43093Same product: Google Android
CVE-2023-21275Same product: Google Android

Affected Assets

google
android
11.0, 12.0, 12.1, 13.0

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.

SC-44 Detonation Chambers
addresses: CWE-470

Externally controlled class or code selection can be resolved and invoked inside the chamber, surfacing unsafe reflection without system impact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover unsafe reflection during code review or scanning.

PR.PS-05 partial match
blocks

Preventing execution of unauthorized code can block exploitation of unsafe reflection at runtime.

PR.PS-06 partial match
blocks

Secure SDLC practices directly avoid introducing externally controlled class selection via reflection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.20 Addressing information security within supplier agreements partial match
removes
A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that can catch/prevent unsafe reflection flaws during development; this stops exploitation for a minority slice (first-party code written under the process) but leaves the bulk of the weakness (e.g. in third-party libraries, legacy code, or incomplete enforcement) untouched.

A.8.26 Application security requirements partial match
blocks

Application security requirements can explicitly prohibit or constrain reflection based on untrusted input.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, least privilege, secure session control, data validation/sanitization, design reviews against attack patterns) that reach a slice of unsafe reflection cases but leave a bounded remainder (e.g. reflection in third-party libraries or dynamic class loading where principles are applied incompletely).

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe reflection and require whitelisting or static alternatives.

References