dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-9365

MEDIUM · 6.5 CVSS v3.0 Published 2025-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A Cross-Site Request Forgery (CSRF) vulnerability in polyaxon/polyaxon v2.4.0 allows attackers to perform unauthorized actions in the context of the victim's browser. This includes creating projects, model versions, and artifact versions, or changing settings. The impact of this vulnerability includes potential data loss and service disruption.

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 · moderate confidence

A CSRF vulnerability in Polyaxon v2.4.0 allows attackers to trick authenticated users into performing unauthorized actions through malicious requests sent from the victim's browser. The application lacks proper anti-CSRF token validation or Origin/Referer header checks on endpoints that create projects, model versions, artifact versions, or modify settings. Attackers can exploit this to perform data manipulation operations in the context of a victim's authenticated session.

MitigationImplement anti-CSRF tokens on all state-changing operations (POST/PUT/DELETE) and validate Origin/Referer headers server-side. Additionally, configure SameSite attribute on session cookies to 'Lax' or 'Strict' to provide defense-in-depth against CSRF attacks.

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
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Polyaxon version
    Run 'polyaxon version' or check the container/docker image version. Alternatively, query the Polyaxon API health endpoint and inspect the version header or response.
    Affected if The installed version is exactly v2.4.0 or falls within the v2.4.x range where the vulnerability exists.
  2. Inspect form submissions for CSRF tokens
    Log into the Polyaxon UI, open browser developer tools, and examine POST/PUT/DELETE requests when creating projects, model versions, artifact versions, or saving settings. Look for a CSRF token parameter in the request body or headers.
    Affected if No CSRF token is present in state-changing requests, indicating the anti-CSRF protection is missing.
  3. Verify Origin or Referer header validation
    Send a crafted request with a mismatched or missing Origin/Referer header to a state-changing endpoint (e.g., /api/v1/projects/) using a tool like curl. Check if the request is accepted without validation.
    Affected if The application accepts requests without validating Origin/Referer headers, allowing cross-origin forged requests.
  4. Check session cookie SameSite attribute
    In browser developer tools, inspect the session cookie (usually named 'polyaxon-session' or similar) under the Application/Storage tab. Examine the cookie attributes for the SameSite setting.
    Affected if The SameSite attribute is set to 'None' or is missing entirely, providing no defense-in-depth against CSRF.
  5. Test affected endpoints for CSRF susceptibility
    Create a proof-of-concept HTML page that automatically submits a form to an affected endpoint (e.g., project creation) while authenticated to Polyaxon. Submit the page from a different origin and verify if the action succeeds.
    Affected if The malicious request succeeds, confirming the CSRF vulnerability is exploitable.

A user is affected if their Polyaxon installation is version 2.4.0 and the application lacks CSRF tokens in requests, does not validate Origin/Referer headers, or does not set SameSite cookies properly on session tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing operations (POST/PUT/DELETE) and validate Origin/Referer headers server-side. Additionally, configure SameSite attribute on session cookies to 'Lax' or 'Strict' to provide defense-in-depth against CSRF attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9365 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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