Unauthenticated API access via nonterminating middleware
Published Mar 18, 2023 · Updated Feb 26, 2025
Authentication bypass in Ansible Semaphore before 2.8.89 allows remote attackers to reach protected API handlers without valid credentials. The authentication middleware writes an HTTP 401 response when validation fails but still calls the downstream handler, so rejected requests continue into protected routes. No privileges or user interaction are required; accessible handler behavior determines which data or administrative operations are exposed.
Summary
What happened
Authentication bypass in Ansible Semaphore before 2.8.89 allows remote attackers to reach protected API handlers without valid credentials. The authentication middleware writes an HTTP 401 response when validation fails but still calls the downstream handler, so rejected requests continue into protected routes. No privileges or user interaction are required; accessible handler behavior determines which data or administrative operations are exposed.
The record
- CVE
- CVE-2023-28609
- Published
- Mar 18, 2023
- Updated
- Feb 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2023CVE publishedPublication date reported by the CVE source.
- Feb 26, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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