CVE-2024-49589
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 · uneditedFoundry Artifacts was found to be vulnerable to a Denial Of Service attack due to disk being potentially filled up based on an user supplied argument (size).
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 confidenceFoundry Artifacts is vulnerable to a Denial of Service attack where an attacker can fill up the disk by specifying a large size argument in a user-supplied request. This allows uncontrolled disk space consumption leading to service unavailability.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Foundry Artifacts installationSearch for Foundry Artifacts processes or services running on the system (e.g., ps aux | grep -i foundry, check for foundry-related services)Affected if Foundry Artifacts is running on the system
-
Determine Foundry Artifacts versionCheck the installed version of Foundry Artifacts (e.g., foundry --version, check package.json, or consult the application's about/version page)Affected if The installed version matches any affected release of Foundry Artifacts (compare against vendor advisory)
-
Verify network accessibility of artifact endpointsCheck if the artifact upload/upload-size API endpoints are exposed to untrusted users (review firewall rules, reverse proxy config, and network ACLs)Affected if The artifact upload functionality is accessible from untrusted networks or users
-
Inspect size parameter validationReview application configuration files and source code for validation on user-supplied size parameters in artifact upload requests (look for maxSize, limit, or validation logic)Affected if No upper bound or strict validation exists on the size parameter in upload requests
-
Check disk usage monitoringReview system monitoring and alerting configuration for disk space (e.g., check if quotas, usage alerts, or write limits are configured for the artifact storage directory)Affected if No disk quota, usage monitoring, or write limits are configured for the artifact storage location
The environment is affected if Foundry Artifacts is running with an exposed upload endpoint that lacks strict validation on user-supplied size parameters and has no disk usage controls.
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 strict validation and upper bounds on the user-supplied size parameter, combined with disk usage monitoring and quota enforcement to prevent unbounded disk writes.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49589 — 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-49589 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