# CVE-2021-31815: Information disclosure in n/a

> Attackers can obtain sensitive location and social graph data from Android system logs due to improper handling of exposure notification identifiers.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vmqv-j6xw-8vh4

## What is CVE-2021-31815?

CVE-2021-31815 is a low-severity vulnerability in n/a, published on 28 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GAEN (aka Google/Apple Exposure Notifications) through 2021-04-27 on Android allows attackers to obtain sensitive information, such as a user's location history, in-person social graph, and (sometimes) COVID-19 infection status, because Rolling Proximity Identifiers and MAC addresses are written to the Android system log, and many Android devices have applications (preinstalled by the hardware manufacturer or network operator) that read system log data and send it to third parties. NOTE: a news outlet (The Markup) states that they received a vendor response indicating that fix deployment "began several weeks ago and will be complete in the coming days."

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2021-31815?

It affects 1 product.


Products: Google Google\/Apple Exposure Notifications.

## How do I fix CVE-2021-31815?

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

## Is CVE-2021-31815 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-31815 and fix it if it is affected.

What it is: CVE-2021-31815 is a low-severity vulnerability in n/a, published on 28 Apr 2021. 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-2021-31815 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-2021-31815/ (Markdown: https://insights.sbomify.com/CVE-2021-31815/index.md)
```

## Sources

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

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