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

> Citrix Gateway allows cache poisoning, though the vendor disputes this as a vulnerability because dynamic content is not cached by default.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cvxg-mfrc-h7wv

## What is CVE-2020-10112?

CVE-2020-10112 is a medium-severity vulnerability in n/a, published on 6 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Citrix Gateway 11.1, 12.0, and 12.1 allows Cache Poisoning. NOTE: Citrix disputes this as not a vulnerability. By default, Citrix ADC only caches static content served under certain URL paths for Citrix Gateway usage. No dynamic content is served under these paths, which implies that those cached pages would not change based on parameter values. All other data traffic going through Citrix Gateway are NOT cached by default

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

It affects 1 product.


Products: Citrix Gateway Firmware.

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

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

## Is CVE-2020-10112 being exploited?

There is no known exploitation of CVE-2020-10112 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-10110](https://insights.sbomify.com/CVE-2020-10110/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10112 is a medium-severity vulnerability in n/a, published on 6 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-10112 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-10112/ (Markdown: https://insights.sbomify.com/CVE-2020-10112/index.md)
```

## Sources

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

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