dbcve.org
ArtifactoryApplication · Jfrog

CVE-2024-2247

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to after 7.77.7 or later.
See remediation →
68/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
JFrog Artifactory versions below 7.77.7, 7.82.1, are vulnerable to DOM-based cross-site scripting due to improper handling of the import override mechanism.

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 below 7.77.7 and 7.82.1 are vulnerable to DOM-based cross-site scripting (XSS) due to improper handling of the import override mechanism. This allows attackers to inject malicious scripts into the DOM through the import functionality, which are then executed in the context of the victim's browser session.

MitigationUpgrade JFrog Artifactory to version 7.77.7, 7.82.1, or later to apply the vendor patch that addresses the improper input sanitization in the import override mechanism.

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
ArtifactoryApplication
Affected:<= 7.77.7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

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

  1. Confirm JFrog Artifactory is installed
    Locate the Artifactory installation by checking for the service process, installation directory, or by accessing the web UI at the standard port (e.g., http://your-server:8082). Check system services or running processes for 'artifactory' or 'jfrog' processes.
    Affected if Artifactory software is present on the system
  2. Identify the installed Artifactory version
    Access the Artifactory web UI, then navigate to the Administration tab and select 'System' > 'General' to view the version information. Alternatively, query the REST API endpoint: /artifactory/api/system/version or check the $ARTIFACTORY_HOME/etc/info.xml file if local access is available.
    Affected if The version displayed is 7.77.7 or lower
  3. Verify the exact version against affected ranges
    Compare your installed version number to the vulnerable ranges: versions 7.77.7 and below are affected. Versions 7.77.8 through 7.82.0 are also vulnerable; only versions 7.77.7 (with patch), 7.82.1, and later are patched.
    Affected if The installed version falls within the vulnerable ranges (any version <= 7.77.7)
  4. Confirm access to import override functionality
    In the Artifactory UI, navigate to Administration > Repositories > Repositories. Check if the import override feature is accessible or configured, typically found in repository settings or import/export sections. This feature allows importing repository configurations or metadata.
    Affected if The import override mechanism is available or has been used in the Artifactory instance

You are affected if JFrog Artifactory is running and its installed version is 7.77.7 or lower, combined with access to the import override feature.

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
Upgrade available Upgrade to a release after 7.77.7
Interim mitigation

Upgrade JFrog Artifactory to version 7.77.7, 7.82.1, or later to apply the vendor patch that addresses the improper input sanitization in the import override mechanism.

Recommended fix Moderate confidence

Artifactory 7.82.1 or later (latest 7.x stable release)

  1. 1. Back up your Artifactory configuration and database according to your organization's backup procedures.
  2. 2. Download JFrog Artifactory version 7.82.1 or the latest 7.x release from the official JFrog distribution.
  3. 3. Stop the Artifactory service.
  4. 4. Install the new Artifactory version following the standard upgrade process for your deployment method (manual, Docker, Helm, or system package).
  5. 5. Start the Artifactory service and verify all repositories and services are operational.
  6. 6. Test the import override functionality to confirm the XSS vulnerability is no longer present.
Caveat Review JFrog release notes for any breaking changes between your current version and 7.82.x; major version upgrades may require migration steps

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

Fix this in Artifactory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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