CVE-2024-8489
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 · uneditedA vulnerability in modelscope/agentscope, specifically in the AgentScope Studio backend server, allows for Cross-Site Request Forgery (CSRF) due to overly permissive CORS headers. This issue affects the latest commit on the main branch (21161fe). The vulnerability permits an attacker to access all backend endpoints, including the `api/file` endpoint, enabling the reading of arbitrary files on the target's local file system through CSRF.
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 confidenceThe AgentScope Studio backend server has overly permissive CORS headers that enable Cross-Site Request Forgery attacks. This allows attackers to make requests from malicious web pages that appear to originate from the vulnerable site, granting access to all backend endpoints including the api/file endpoint which can be leveraged to read arbitrary files from the server's local file system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify AgentScope Studio installationLocate the AgentScope Studio backend server installation directory and identify the server configuration files (typically found in the project root or config directory). Look for files named app.py, server.py, or similar entry points that initialize the backend server.Affected if AgentScope Studio backend server is present and running
-
Check CORS configuration in server codeSearch the server source files for CORS configuration. Look for calls to cors.init_app(), cors = CORS(), or similar CORS initialization code. Examine the parameters passed, particularly any origin settings.Affected if The CORS configuration allows wildcard (*) origins or lacks explicit origin whitelist
-
Inspect HTTP responses for CORS headersSend a cross-origin HTTP request to any backend endpoint (such as GET /api/health or GET /) with an arbitrary Origin header (e.g., Origin: http://malicious-site.com) and examine the response headers. Use curl -H 'Origin: http://example.com' -I <backend_url> to inspect headers.Affected if The response includes Access-Control-Allow-Origin: * or echoes back the arbitrary origin without validation
-
Verify api/file endpoint is exposedCheck if the /api/file endpoint exists by reviewing route definitions in the server code or attempting to access it. Look for route decorators like @app.route('/api/file') or file download/upload handlers.Affected if The /api/file endpoint is accessible without authentication or proper origin validation
-
Confirm lack of CSRF protectionExamine the server code for CSRF token implementation. Check if state-changing endpoints (POST, PUT, DELETE) validate CSRF tokens or have SameSite cookie attributes configured.Affected if State-changing operations lack CSRF token validation and cookies lack SameSite=Strict or SameSite=Lax attributes
You are affected if AgentScope Studio backend server is running with CORS configured to allow arbitrary origins (*), which enables cross-origin attacks to access the api/file endpoint for arbitrary file read.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict CORS headers to only allow trusted origins, implement CSRF tokens for state-changing operations, and validate the Referer/Origin headers on sensitive endpoints like api/file.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8489 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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