CVE-2022-23206Network attack vector

Unauthenticated SSRF via OAuth login POST

Published Feb 6, 2022 · Updated Aug 3, 2024

Server-Side Request Forgery in Apache Traffic Control Traffic Ops before 5.1.6 or 6.1.0 allows remote attackers to scan ports via HTTPS. The POST /user/login/oauth handler accepts attacker-controlled OAuth login data and causes Traffic Ops to connect to a chosen host and port, exposing reachability of systems on the server's network. Any unprivileged account that can reach Traffic Ops over HTTPS can trigger the scan; the documented impact is network reconnaissance rather than data modification or service interruption.

CVSS severity7.5
High
EPSS probability1.98%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Server-Side Request Forgery in Apache Traffic Control Traffic Ops before 5.1.6 or 6.1.0 allows remote attackers to scan ports via HTTPS. The POST /user/login/oauth handler accepts attacker-controlled OAuth login data and causes Traffic Ops to connect to a chosen host and port, exposing reachability of systems on the server's network. Any unprivileged account that can reach Traffic Ops over HTTPS can trigger the scan; the documented impact is network reconnaissance rather than data modification or service interruption.

The record

CVE
CVE-2022-23206
Published
Feb 6, 2022
Updated
Aug 3, 2024
Vendor
The Apache Software Foundation
Product
Apache Traffic Control
Classifications
CWE-918, T1190, T1046
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 6, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Traffic Ops <6.1.0 changes=[{"at":"5.1.6","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

The Apache Software Foundation · Apache Traffic Controlversion=Traffic Ops <6.1.0 changes=[{"at":"5.1.6","status":"unaffected"}]

Published CVSS scores

7.5GitLab Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application
T1046Network Service Scanning

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo