dbcve.org
Traffic ControlApplication · Apache

CVE-2022-23206

HIGH · 7.5 CVSS v3.1 Published 2022-02-06
Fix available
A fix is available. Upgrade to 5.1.6 / 6.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged user who can reach Traffic Ops over HTTPS can send a specially-crafted POST request to /user/login/oauth to scan a port of a server that Traffic Ops can reach.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in Apache Traffic Control Traffic Ops. An unauthenticated or unprivileged user with HTTPS access to Traffic Ops can send a crafted POST request to the /user/login/oauth endpoint, allowing them to scan arbitrary ports on servers that Traffic Ops can reach. This enables attackers to discover internal infrastructure and services that would otherwise be inaccessible due to network segmentation.

MitigationUpgrade Traffic Ops to version 6.1.0 or later (for 6.x) or 5.1.6 or later (for 5.x). Alternatively, restrict HTTPS access to Traffic Ops to only trusted users and implement network-level controls to limit which servers the Traffic Ops service can communicate with.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Traffic ControlApplication
Affected:< 5.1.6>= 6.0.0, < 6.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Traffic Ops version
    Check the installed version of Apache Traffic Control or Traffic Ops package on your server. Common ways include: running 'traffic_ops_golang --version', checking the RPM/DEB package version, or reviewing the version in the traffic_ops_golang binary.
    Affected if The installed version is < 5.1.6 OR >= 6.0.0 and < 6.1.0
  2. Verify HTTPS access to Traffic Ops
    Confirm that Traffic Ops is accessible via HTTPS. Check your reverse proxy or load balancer configuration, and test connectivity to the Traffic Ops host over HTTPS.
    Affected if Traffic Ops HTTPS endpoint is exposed to untrusted users or the public network
  3. Confirm OAuth login endpoint is enabled
    Inspect the Traffic Ops configuration files (typically in /opt/traffic_ops/conf or /etc/traffic_ops) for the OAuth login plugin or module settings. Look for 'oauth' or 'user/login/oauth' in the configuration.
    Affected if OAuth-based login is configured and the /user/login/oauth endpoint is active
  4. Check access controls on Traffic Ops
    Review network-level access controls, firewall rules, and Traffic Ops authentication settings. Determine if unauthenticated or unprivileged users can reach the HTTPS endpoint.
    Affected if Unauthenticated or unprivileged users can access the Traffic Ops HTTPS interface without sufficient restrictions

You are affected if Traffic Ops version is < 5.1.6 or >= 6.0.0 but < 6.1.0 AND the HTTPS endpoint with OAuth login is accessible to untrusted or unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.1.6 / 6.1.0 or later
Fixed in 5.1.66.1.0
Interim mitigation

Upgrade Traffic Ops to version 6.1.0 or later (for 6.x) or 5.1.6 or later (for 5.x). Alternatively, restrict HTTPS access to Traffic Ops to only trusted users and implement network-level controls to limit which servers the Traffic Ops service can communicate with.

Recommended fix High confidence

Upgrade to Traffic Control 5.1.6 (for 5.x branches) or 6.1.0 (for 6.x branches)

  1. Backup the Traffic Ops configuration files, database, and any custom scripts
  2. Stop the Traffic Ops service
  3. Upgrade to Traffic Control 5.1.6 (if currently on 5.x) or 6.1.0 (if currently on 6.x) using your system's package manager or by downloading from the Apache Traffic Control releases
  4. Verify all dependencies are also updated to compatible versions
  5. Start the Traffic Ops service
  6. Verify the /user/login/oauth endpoint no longer allows arbitrary port scanning (or test that SSRF is no longer possible)
Caveat Review Apache Traffic Control release notes for 5.1.6 and 6.1.0 for any breaking changes, configuration file updates, or API changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traffic Control Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
21.0 hours of engineering $3,660
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23206 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data