CVE-2022-1130: Insufficient validation of untrusted input in WebOTP
Insufficient validation of trust input in WebOTP in Google Chrome on Android prior to 100.0.4896.60 allowed a remote attacker to send arbitrary intents from any app via a malicious app.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 100.0.4896.60 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 100.0.4896.60-1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2022-1130?
CVE-2022-1130 is considered a high-severity vulnerability due to its potential to exploit trust validation issues in WebOTP.
How do I fix CVE-2022-1130?
To fix CVE-2022-1130, users should update Google Chrome to version 100.0.4896.60 or later.
What does CVE-2022-1130 affect?
CVE-2022-1130 affects Google Chrome versions prior to 100.0.4896.60 on Android.
Can CVE-2022-1130 allow remote code execution?
Yes, CVE-2022-1130 can allow a remote attacker to send arbitrary intents, which can potentially lead to remote code execution.
Is my Android device vulnerable to CVE-2022-1130?
CVE-2022-1130 specifically affects the WebOTP feature in vulnerable versions of Google Chrome installed on Android devices.