LDAP filter injection vulnerability in Traffic Ops
Apache Software Foundation Apache Traffic Control
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/apache/trafficcontrol Go |
|
|
Apache Software Foundation Apache Traffic Control
| Product | Affected | Fixed in |
|---|---|---|
| github.com/apache/trafficcontrol Go |
|
|
6.0.1+incompatibleAn unauthenticated Apache Traffic Control Traffic Ops user can send a request with a specially-crafted username to the POST /login endpoint of any API version to inject unsanitized content into the LDAP filter.
From the CVE record · apache
Apache Traffic Control Traffic Ops does not sanitize usernames before inserting them into an LDAP filter at the POST /login endpoint, across all API versions. An unauthenticated remote requester can submit a specially crafted username to inject content into the filter; no user interaction is described.
Teams running Apache Traffic Control with Go package github.com/apache/trafficcontrol versions >=6.0.0 <6.0.1, >=5.1.0 <5.1.4, >=5.1.0+incompatible <5.1.4+incompatible, or >=6.0.0+incompatible <6.0.1+incompatible should check their deployments.