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

> The GAEN protocol allows attackers to coerce users into revealing their exposure notification status due to persistent private framework state.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9pjj-6grx-8qjx

## What is CVE-2020-24721?

CVE-2020-24721 is a medium-severity vulnerability in n/a, published on 30 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in the GAEN (aka Google/Apple Exposure Notifications) protocol through 2020-09-29, as used in COVID-19 applications on Android and iOS. It allows a user to be put in a position where he or she can be coerced into proving or disproving an exposure notification, because of the persistent state of a private framework.

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

It affects 2 products.


Products: Apple Exposure Notifications, Google Exposure Notifications.

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

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

## Is CVE-2020-24721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24721 is a medium-severity vulnerability in n/a, published on 30 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-24721 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-24721/ (Markdown: https://insights.sbomify.com/CVE-2020-24721/index.md)
```

## Sources

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

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