# Cache Manipulation Attack in Apache Traffic Control

Advisory record · `GHSA-pw59-4qgf-jxr8`

- **Identifiers:** `GHSA-pw59-4qgf-jxr8` · `CVE-2020-17522`
- **State:** Confirmed
- **Severity:** CVSS 5.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-525](https://cwe.mitre.org/data/definitions/525.html) · [CWE-732](https://cwe.mitre.org/data/definitions/732.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-525](https://agentprime.io/advisories/tag/cwe-525.md)
- **Published:** 18 Jun 2021
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Jun 2021, 22:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/apache/trafficcontrol` (Go): affected `<5.0.0`; fixed in `5.0.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.040, the 90th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 18 Jun 2021. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-pw59-4qgf-jxr8](https://github.com/advisories/GHSA-pw59-4qgf-jxr8)
- [OSV: GHSA-pw59-4qgf-jxr8](https://osv.dev/vulnerability/GHSA-pw59-4qgf-jxr8)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-17522>
- <https://github.com/apache/trafficcontrol/commit/492290d810e9608afb5d265b98cd3f3e153e776b>
- <https://github.com/apache/trafficcontrol>
- <https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E>
- <https://lists.apache.org/thread.html/r3de212a3da73bcf98fa2db7eafb75b2eb8e131ff466e6efc4284df09%40%3Cdev.trafficcontrol.apache.org%3E>
- <https://lists.apache.org/thread.html/rc8bfd7d4f71d61e9193efcd4699eccbab3c202ec1d75ed9d502f08bf@%3Ccommits.trafficcontrol.apache.org%3E>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pw59-4qgf-jxr8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pw59-4qgf-jxr8/>. Everything for agents: <https://agentprime.io/llms.txt>.