# CVE-2012-2808: Weak cryptography in n/a

> Weak PRNG in Android DNS resolver allows remote attackers to spoof DNS responses by guessing query IDs and source ports.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wr4x-7qhj-2g7g

## What is CVE-2012-2808?

CVE-2012-2808 is a medium-severity vulnerability in n/a, published on 1 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PRNG implementation in the DNS resolver in Bionic in Android before 4.1.1 incorrectly uses time and PID information during the generation of random numbers for query ID values and UDP source ports, which makes it easier for remote attackers to spoof DNS responses by guessing these numbers, a related issue to CVE-2015-0800.

## Which versions are affected by CVE-2012-2808?

It affects 1 product.


Products: Google Bionic.

## How do I fix CVE-2012-2808?

Upgrade to a fixed version.

## Is CVE-2012-2808 being exploited?

There is no known exploitation of CVE-2012-2808 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-2674](https://insights.sbomify.com/CVE-2012-2674/): Integer overflow in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2808 and fix it if it is affected.

What it is: CVE-2012-2808 is a medium-severity vulnerability in n/a, published on 1 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2808 in the wild and no public exploit code.

Affected product: n/a. 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-2012-2808/ (Markdown: https://insights.sbomify.com/CVE-2012-2808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2808
- OSV: https://osv.dev/vulnerability/CVE-2012-2808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2808/
Summaries are generated and may contain mistakes; the official description above is the record.