CVE-2021-42009 json
Apache Traffic Control Traffic Ops Email Injection Vulnerability
published 2021-10-12 5 y ago modified 2026-06-17 4 mo ago also GHSA-gw97-f6h8-gm94 , GO-2022-0602 , EUVD-2021-2206
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
An authenticated Apache Traffic Control Traffic Ops user with Portal-level privileges can send a request with a specially-crafted email subject to the /deliveryservices/request Traffic Ops endpoint to send an email, from the Traffic Ops server, with an arbitrary body to an arbitrary email address. Apache Traffic Control 5.1.x users should upgrade to 5.1.3 or 6.0.0. 4.1.x users should upgrade to 5.1.3.
Patch / fix
- go github.com/apache/trafficcontrol 5.1.3, 5.1.3+incompatible
- apache traffic_control 5.1.3
Exploit prediction
2.82% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/apache/trafficcontrol | <5.1.3 <5.1.3+incompatible |
5.1.3 5.1.3+incompatible |
Affected products
- Apache Software Foundation Apache Traffic Control
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
lists.apache.org
/thread.html/rf0481b9e38ece1ece458d3ce7b2d671df819e3555597f31fc34f084e%40%3Ccommits.trafficcontrol.apache.org%
web, mailing-list, patch, vendor-advisory
-
lists.apache.org
/thread.html/re384fd0f44c6d230f31376153c6e8b59e4a669f927c1533d06d702af%40%3Cdev.trafficcontrol.apache.org%3E
web, mailing-list, vendor-advisory
-
openwall.com
/lists/oss-security/2021/10/12/1
mailing-list, web, third-party-advisory
-
lists.apache.org
/thread.html/r78d471d8a4fd268a4c5ae6c47327c09d9d4b4467c31da2c97422febb%40%3Cdev.trafficcontrol.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/r7dfa9a89b39d06caeeeb7b5cdc41b3493a9b86cc6cfa059d3f349d87%40%3Cannounce.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2021-42009
advisory
-
github.com
/apache/trafficcontrol
package
-
lists.apache.org
/thread.html/r78d471d8a4fd268a4c5ae6c47327c09d9d4b4467c31da2c97422febb@%3Cdev.trafficcontrol.apache.org%3E
web
-
lists.apache.org
/thread.html/r7dfa9a89b39d06caeeeb7b5cdc41b3493a9b86cc6cfa059d3f349d87@%3Cannounce.apache.org%3E
web
-
github.com
/advisories/GHSA-gw97-f6h8-gm94
advisory
Sources
- CVE List CVE-2021-42009
- GitHub Advisory GHSA-gw97-f6h8-gm94
- NVD CVE-2021-42009
- OSV GO-2022-0602
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.