CVE-2016-3818 libc in Android 4.x before 4.4.4 allows remote attackers to cause a denial of service (device hang or reboot) via a crafted file, aka internal bug 28740702.
Medium 5.5
Published
Updated
Check this codebase for CVE-2016-3818 and fix it if it is affected.
What it is: CVE-2016-3818 is a medium-severity vulnerability in Google Android, published on 11 Jul 2016.
Exploitation: There is no known exploitation of CVE-2016-3818 in the wild and no public exploit code.
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-2016-3818/ (Markdown: https://insights.sbomify.com/CVE-2016-3818/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2016-3818?
CVE-2016-3818 is a medium-severity vulnerability in Google Android, published on 11 Jul 2016.
Official description
libc in Android 4.x before 4.4.4 allows remote attackers to cause a denial of service (device hang or reboot) via a crafted file, aka internal bug 28740702.
Weakness: CWE-284
Which versions are affected by CVE-2016-3818?
It affects 1 product.
Products include Google Android.
How do I fix CVE-2016-3818?
No fix has been published for CVE-2016-3818 yet. Limit exposure of the affected software until one is available.
Is CVE-2016-3818 being exploited?
There is no known exploitation of CVE-2016-3818 in the wild and no public exploit code.
Other vulnerabilities in Google Android
Sources
Also known as GHSA-pfq2-wh4j-r5cm, UBUNTU-CVE-2016-3818.