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

> Citrix Gateway exposes cache metadata via HTTP headers, though the vendor disputes this as sensitive information disclosure.

- **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:** 6 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gjfq-q65w-382h

## What is CVE-2020-10110?

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

### Official description

Citrix Gateway 11.1, 12.0, and 12.1 allows Information Exposure Through Caching. NOTE: Citrix disputes this as not a vulnerability. There is no sensitive information disclosure through the cache headers on Citrix ADC. The "Via" header lists cache protocols and recipients between the start and end points for a request or a response. The "Age" header provides the age of the cached response in seconds. Both headers are commonly used for proxy cache and the information is not sensitive

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

It affects 1 product.


Products: Citrix Gateway Firmware.

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

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

## Is CVE-2020-10110 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10111](https://insights.sbomify.com/CVE-2020-10111/): Other in n/a (high 7.5)
- [CVE-2020-10112](https://insights.sbomify.com/CVE-2020-10112/): Other in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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