dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-6915

CRITICAL · 9.3 CVSS v3.1 Published 2024-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
JFrog Artifactory versions below 7.90.6, 7.84.20, 7.77.14, 7.71.23, 7.68.22, 7.63.22, 7.59.23, 7.55.18 are vulnerable to Improper Input Validation that could potentially lead to cache poisoning.

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 confidence

JFrog Artifactory versions prior to 7.90.6 (and other fixed versions) contain an improper input validation vulnerability that could allow attackers to manipulate cache data through specially crafted input, potentially leading to cache poisoning attacks.

MitigationUpgrade JFrog Artifactory to version 7.90.6 or higher (or to one of the other fixed versions: 7.84.20, 7.77.14, 7.71.23, 7.68.22, 7.63.22, 7.59.23, or 7.55.18) to remediate this vulnerability.

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
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L

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 the installed JFrog Artifactory version
    Access the Artifactory admin UI and navigate to the 'System Information' or 'About' section, or use the REST API endpoint '/api/system/version' to retrieve the running version number
    Affected if The displayed version is earlier than 7.90.6 (or matches any of these versions: 7.84.20, 7.77.14, 7.71.23, 7.68.22, 7.63.22, 7.59.23, 7.55.18)
  2. Confirm the exact version string
    Note the full version number including any patch or build suffixes shown in the version information
    Affected if The version string starts with a number lower than 7.90.6 when compared numerically, or exactly matches one of the listed vulnerable versions
  3. Verify if caching features are in use
    Check whether Artifactory caching for remote repositories or the general HTTP cache is enabled and actively used in your deployment
    Affected if Cache functionality is enabled and remote repository caching or HTTP caching is configured, since the vulnerability involves manipulation of cache data

You are affected if your Artifactory version is 7.90.6 or lower and caching features are enabled, with versions prior to 7.90.6 being the most vulnerable.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JFrog Artifactory to version 7.90.6 or higher (or to one of the other fixed versions: 7.84.20, 7.77.14, 7.71.23, 7.68.22, 7.63.22, 7.59.23, or 7.55.18) to remediate this vulnerability.

Recommended fix High confidence

Upgrade to version 7.90.6 (or at minimum 7.84.20, 7.77.14, 7.71.23, 7.68.22, 7.63.22, 7.59.23, or 7.55.18 depending on your current version branch)

  1. Identify the currently installed JFrog Artifactory version by checking the Artifactory UI (Administration > System > General) or the $ARTIFACTORY_HOME/etc/info.xml file
  2. Determine which upgrade path applies based on your current version (see upgrade_path for target versions)
  3. Review JFrog's upgrade documentation and release notes for the target version
  4. Plan maintenance window as upgrade requires service restart
  5. Back up the Artifactory home directory and database before upgrading
  6. For Linux/Unix: Stop the Artifactory service using 'systemctl stop artifactory' or 'service artifactory stop'
  7. For Linux/Unix: Run the installer for the target version (e.g., using RPM/DEB package or JFrog CLI)
  8. For Windows: Stop the Artifactory Windows service and run the installer executable
Caveat Review JFrog release notes for breaking changes between your current version and target version; major version jumps may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6915 — 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-6915 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