CVE-2013-6792 Security feature bypass in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2013-6792 and fix it if it is affected.
What it is: CVE-2013-6792 is a critical vulnerability in Google Android, published on 23 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6792 exists.
Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2013-6792/ (Markdown: https://insights.sbomify.com/CVE-2013-6792/index.md)
Attackers can bypass APK signature verification in Android, allowing installation of malicious or modified applications.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2013-6792?
CVE-2013-6792 is a critical vulnerability in Google Android, published on 23 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Google Android prior to 4.4 has an APK Signature Security Bypass Vulnerability
Which versions are affected by CVE-2013-6792?
It affects 1 product.
Products include Google Android.
How do I fix CVE-2013-6792?
No fix has been published for CVE-2013-6792 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-6792 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6792 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in Google Android
Sources
Also known as GHSA-fpf2-3qcv-7h5q.