Vulnerability Database · Go · github.com/apache/trafficcontrol · Version
github.com/apache/trafficcontrol v1.1.4-0.20220907183905-5e8255fee5ee
v1.1.4-0.20220907183905-5e8255fee5ee is affected by 6 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: v7.0.1+incompatible.
Critical 0 High 0 Medium 2 Low 0 Unrated 4
-
Released 07 Sep 2022
Licence Apache-2.0
Also known from other sources 7
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the Go module proxy. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
github.com/apache/trafficcontrol v1.1.4-0.20220907183905-5e8255fee5ee vulnerabilities
6 vulnerabilities cover github.com/apache/trafficcontrol v1.1.4-0.20220907183905-5e8255fee5ee. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-17522: Cache Manipulation Attack in Apache Traffic Control | 5.8 medium | 5.0.0 | 18 Jun 2021 |
| CVE-2021-42009: Email relay in Apache Traffic Control | 4.3 medium | 5.1.3 | 13 Oct 2021 |
| CVE-2025-61581: Apache Traffic Control Inefficient Regular Expression Complexity Vulnerability | N/A unrated | No fix published | 30 Oct 2025 |
| CVE-2024-45387: SQL Injection Vulnerability in Apache Traffic Control Package | N/A unrated | No fix published | 07 Jan 2025 |
| Server-Side Request Forgery in Apache Traffic Control | N/A unrated | 5.1.6+incompatible | 21 Aug 2024 |
| Email Relay Vulnerability in Apache Traffic Control | N/A unrated | 5.1.3+incompatible | 21 Aug 2024 |
Looking for another version, or everything Vulert holds for github.com/apache/trafficcontrol?
Questions
About github.com/apache/trafficcontrol v1.1.4-0.20220907183905-5e8255fee5ee
Is github.com/apache/trafficcontrol v1.1.4-0.20220907183905-5e8255fee5ee vulnerable?
Yes. 6 vulnerabilities in the Vulert database cover github.com/apache/trafficcontrol v1.1.4-0.20220907183905-5e8255fee5ee: 0 critical, 0 high, 2 medium and 0 low, plus 4 not yet rated. The upgrade Vulert recommends is v7.0.1+incompatible, and each entry above names the fixed version to move to.
Which version of github.com/apache/trafficcontrol should I use instead of v1.1.4-0.20220907183905-5e8255fee5ee?
v7.0.1+incompatible is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is v1.1.4-0.20220907183905-5e8255fee5ee the latest release of github.com/apache/trafficcontrol?
No. v1.1.4-0.20220907183905-5e8255fee5ee was published 07 Sep 2022, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor github.com/apache/trafficcontrol for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/apache/trafficcontrol version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.