# CVE-2020-12859: Information disclosure in n/a

> Remote attackers can identify specific device models via cleartext protocol data, enabling user re-identification in low-density scenarios.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** No
- **Published:** 18 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q86j-858x-v75c

## What is CVE-2020-12859?

CVE-2020-12859 is a medium-severity vulnerability in n/a, published on 18 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unnecessary fields in the OpenTrace/BlueTrace protocol in COVIDSafe through v1.0.17 allow a remote attacker to identify a device model by observing cleartext payload data. This allows re-identification of devices, especially less common phone models or those in low-density situations.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Health Covidsafe.

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

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

## Is CVE-2020-12859 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12857](https://insights.sbomify.com/CVE-2020-12857/): Information disclosure in n/a (high 7.5)
- [CVE-2020-12858](https://insights.sbomify.com/CVE-2020-12858/): Information disclosure in n/a (high 7.5)
- [CVE-2020-14292](https://insights.sbomify.com/CVE-2020-14292/): Information disclosure in n/a (medium 5.7)
- [CVE-2020-12860](https://insights.sbomify.com/CVE-2020-12860/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12859 is a medium-severity vulnerability in n/a, published on 18 May 2020. 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-2020-12859 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-12859/ (Markdown: https://insights.sbomify.com/CVE-2020-12859/index.md)
```

## Sources

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

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