Arbitrary file disclosure via permissive CORS headers
Published Mar 20, 2025 · Updated Mar 20, 2025
Cross-site request forgery in AgentScope Studio at commit 21161fe allows remote attackers to read arbitrary local files through its API. The Studio backend applies overly permissive CORS headers to every endpoint instead of restricting trusted origins, allowing a malicious origin to call api/file. A victim must load attacker-controlled content while the backend is reachable from the victim's browser; the demonstrated consequence is arbitrary local-file disclosure.
Summary
What happened
Cross-site request forgery in AgentScope Studio at commit 21161fe allows remote attackers to read arbitrary local files through its API. The Studio backend applies overly permissive CORS headers to every endpoint instead of restricting trusted origins, allowing a malicious origin to call api/file. A victim must load attacker-controlled content while the backend is reachable from the victim's browser; the demonstrated consequence is arbitrary local-file disclosure.
The record
- CVE
- CVE-2024-8489
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- ModelScope
- Product
- AgentScope
- Classifications
- CWE-352, T1190
- 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 <=latest
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.
Weakness, pattern, technique
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