API data exposure via wildcard CORS allowlists
Published Mar 20, 2025 · Updated Mar 20, 2025
CORS misconfiguration in Prefect before 2.20.17 and 3.0.0rc1 through 3.0.2 allows remote attackers to read API data via a browser. The server's CORSMiddleware hard-codes wildcard origin, method, and header allowlists, so browsers permit cross-origin API requests from attacker-controlled sites. Exploitation requires a user with network access to the server to load attacker-controlled content; exposed API data can then be read, modified, or used to interrupt service.
Summary
What happened
CORS misconfiguration in Prefect before 2.20.17 and 3.0.0rc1 through 3.0.2 allows remote attackers to read API data via a browser. The server's CORSMiddleware hard-codes wildcard origin, method, and header allowlists, so browsers permit cross-origin API requests from attacker-controlled sites. Exploitation requires a user with network access to the server to load attacker-controlled content; exposed API data can then be read, modified, or used to interrupt service.
The record
- CVE
- CVE-2024-8183
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- Prefect Technologies, Inc.
- Product
- Prefect
- Classifications
- CWE-346, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Public exploit references
- Huntr browser-based CORS proof of conceptproof of concept · demonstrated
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