CVE-2022-23206 json
Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth
published 2022-02-06 4 y ago modified 2026-06-17 4 mo ago also GHSA-wp47-9r3h-xfgq , GO-2022-0585 , EUVD-2022-1233
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged user who can reach Traffic Ops over HTTPS can send a specially-crafted POST request to /user/login/oauth to scan a port of a server that Traffic Ops can reach.
Patch / fix
- go github.com/apache/trafficcontrol 5.1.6, 5.1.6+incompatible, 6.1.0, 6.1.0+incompatible
- Apache Software Foundation Apache Traffic Control 5.1.6, 6.1.0
Exploit prediction
1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/apache/trafficcontrol | >=6.0.0, <6.1.0 <5.1.6 <5.1.6+incompatible >=6.0.0+incompatible, <6.1.0+incompatible |
6.1.0 5.1.6 5.1.6+incompatible 6.1.0+incompatible |
Affected products
- Apache Software Foundation Apache Traffic Control
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
lists.apache.org
/thread/lsrd2mqj29vrvwsh8g0d560vvz8n126f
web, mailing-list, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-23206
advisory
-
github.com
/advisories/GHSA-wp47-9r3h-xfgq
advisory
Sources
- CVE List CVE-2022-23206
- GitHub Advisory GHSA-wp47-9r3h-xfgq
- NVD CVE-2022-23206
- OSV GO-2022-0585
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.