Improper Authentication in Apache Traffic Control

published 2019-09-09 7 y ago modified 2026-06-17 4 mo ago also GHSA-3f8r-4qwm-r7jf , EUVD-2021-0918

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.5%; EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits: 0; none known

Improper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password.

Patch / fix

fixed in 1 links 1

go github.com/apache/trafficcontrol 3.0.2-RC1

github.com/apache/trafficcontrol@f780aff commit

Exploit prediction

3.45% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
go	github.com/apache/trafficcontrol	>=3.0.0, <3.0.2-RC1	3.0.2-RC1

Affected products

Apache Traffic Control

Classification

Weakness

CWE-287 Improper Authentication

References

Sources

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.

Summary