CVE-2024-39272
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 cross-site scripting (xss) vulnerability exists in the dataset upload functionality of ClearML Enterprise Server 3.22.5-1533. A specially crafted HTTP request can lead to an arbitrary html code. An attacker can send a series of HTTP requests to trigger this vulnerability.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the dataset upload functionality of ClearML Enterprise Server 3.22.5-1533. The application fails to properly sanitize or validate user input during the dataset upload process, allowing attackers to inject arbitrary HTML/JavaScript code via crafted HTTP requests. This stored XSS could execute in the browsers of other users viewing the uploaded content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.22.5-1533CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ClearML Enterprise Server versionRun 'clearml-server --version' or check the Docker container image tag, or look in the application admin panel for the server version informationAffected if The installed version is exactly 3.22.5-1533
-
Verify dataset upload feature is accessibleCheck if the dataset upload functionality is enabled in the server configuration and accessible to users via the web UI or API endpointAffected if The dataset upload feature is enabled and users can upload files to the server
-
Inspect existing uploaded datasets for suspicious contentNavigate to the datasets section in the ClearML web interface or query the backend storage/database for uploaded files. Examine file names, metadata, or content for HTML script tags, JavaScript event handlers, or encoded XSS payloadsAffected if Any uploaded datasets contain unencoded HTML, JavaScript, or suspicious encoded strings that could execute in a browser
-
Review server access logs for XSS exploitation attemptsExamine web server logs (typically in /var/log/ or Docker container logs) for POST requests to dataset upload endpoints containing patterns like <script>, javascript:, onerror=, or other HTML/JS injection vectorsAffected if Logs show HTTP requests to upload endpoints with XSS payload patterns in the request parameters
You are affected if your ClearML Enterprise Server is exactly version 3.22.5-1533 and the dataset upload feature is enabled, particularly if you find suspicious content in uploaded datasets or exploitation attempts in your logs.
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 dataImplement proper input validation and output encoding for all user-supplied data in the dataset upload functionality. Use context-appropriate HTML encoding and consider implementing Content Security Policy (CSP) headers to mitigate XSS risks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39272 — 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-39272 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