# CVE-2020-12270: Other in n/a

> Weak random ID generation in Bluezone allows attackers to spam false contact alerts, though the vendor disputes the severity due to verification mechanisms.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-63h7-pm69-6v2j

## What is CVE-2020-12270?

CVE-2020-12270 is a medium-severity vulnerability in n/a, published on 27 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

React Native Bluetooth Scan in Bluezone 1.0.0 uses six-character alphanumeric IDs, which might make it easier for remote attackers to interfere with COVID-19 contact tracing by using many IDs. NOTE: the vendor disputes the relevance of this report because the recipient of an F1 alert will know it was a false alert if contact-history comparison fails (i.e., an F0 is not actually part of the contact history obtained from the device of this recipient, or this recipient is not actually part of the contact history obtained from the device of an F0)

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2020-12270?

It affects 1 product.


Products: Bluezone Bluezone.

## How do I fix CVE-2020-12270?

No fix has been published for CVE-2020-12270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-12270 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12270 and fix it if it is affected.

What it is: CVE-2020-12270 is a medium-severity vulnerability in n/a, published on 27 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12270 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-2020-12270/ (Markdown: https://insights.sbomify.com/CVE-2020-12270/index.md)
```

## Sources

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

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