Code execution via malicious service binding
Published Mar 1, 2023 · Updated Mar 7, 2025
Code injection in Google YouTube Android Player API 1.2 through 1.2.2 allows attackers to execute code through a malicious app. The SDK can bind to an app masquerading as YouTube, create a security-ignoring remote context, and load that app's ClassLoader into the caller. Exploitation requires the victim to install both the masquerading app and an app using the embedded player, after which invoking the SDK runs attacker-controlled code.
Summary
What happened
Code injection in Google YouTube Android Player API 1.2 through 1.2.2 allows attackers to execute code through a malicious app. The SDK can bind to an app masquerading as YouTube, create a security-ignoring remote context, and load that app's ClassLoader into the caller. Exploitation requires the victim to install both the masquerading app and an app using the embedded player, after which invoking the SDK runs attacker-controlled code.
The record
- CVE
- CVE-2023-0460
- Published
- Mar 1, 2023
- Updated
- Mar 7, 2025
- Vendor
- Product
- YouTube Android Player API
- Classifications
- CWE-470, CAPEC-253, T1620
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2 <=1.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo