CVE-2019-12405: Improper Authentication in Apache Traffic Control

CVE-2019-12405 · Severity: low · CVSS 3.1 · Published 2021-05-18

Improper Authentication in Apache Traffic Control

Technologies: github.com/apache/trafficcontrol (Go). Vendors: Go.

Quick answers

Is CVE-2019-12405 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-12405 being exploited in the wild.
How severe is CVE-2019-12405?
Low severity, with a CVSS score of 3.1, published 18 May 2021.
Which products and versions are affected?
github.com/apache/trafficcontrol (Go) SEMVER:introduced=3.0.0,fixed=3.0.2-RC1.
Is there a fix for CVE-2019-12405?
Yes. github.com/apache/trafficcontrol (Go): upgrade to 3.0.2-RC1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-12405?
Check whether you run github.com/apache/trafficcontrol (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/apache/trafficcontrol (Go): upgrade to 3.0.2-RC1 or later
    go get github.com/apache/trafficcontrol@v3.0.2-RC1

Affected products

  • github.com/apache/trafficcontrol (Go) SEMVER:introduced=3.0.0,fixed=3.0.2-RC1

Identifiers

  • CVE-2019-12405
  • GHSA-3f8r-4qwm-r7jf

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.