dbcve.org
ArtifactoryApplication · Jfrog

CVE-2023-42661

HIGH · 8.8 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 7.76.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 prior to version 7.76.2 is vulnerable to Arbitrary File Write of untrusted data, which may lead to DoS or Remote Code Execution when a specially crafted series of requests is sent by an authenticated user. This is due to insufficient validation of artifacts.

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 prior to version 7.76.2 contains an arbitrary file write vulnerability where authenticated users can send specially crafted artifact uploads that bypass validation checks, allowing writing untrusted data to arbitrary filesystem locations. This can lead to denial of service or remote code execution.

MitigationUpgrade JFrog Artifactory to version 7.76.2 or later to remediate the insufficient artifact validation. Prior to upgrade, restrict administrative access and monitor for suspicious artifact upload patterns.

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.76.2

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

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

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

  1. Determine installed Artifactory version
    Run 'artifactoryctl version' or check the $ARTIFACTORY_HOME/etc/info.json file for the 'version' field
    Affected if The installed version is prior to 7.76.2 (for example, 7.75.0, 7.70.0, etc.)
  2. Verify Artifactory is accessible via web UI or API
    Access the Artifactory web interface or REST API endpoint (for example, /artifactory/api/system/version) to confirm the service is running
    Affected if Artifactory is running and accessible - the vulnerability requires an authenticated session to exploit
  3. Identify users with upload permissions
    Review user permissions in Artifactory admin console under 'Identity and Access > Users' and 'Identity and Access > Groups' for accounts with 'Deploy' or 'Upload' permissions
    Affected if There are any non-admin or non-service accounts with upload/deploy permissions enabled
  4. Review audit logs for suspicious artifact uploads
    Check Artifactory audit logs in $ARTIFACTORY_HOME/logs/audit.log for unusual upload patterns, especially uploads containing path traversal patterns (such as '../') or writes to non-standard directories
    Affected if Audit logs show artifact uploads with abnormal paths or high-volume uploads from a single user
  5. Check for unexpected files in filesystem
    Inspect $ARTIFACTORY_HOME/var/data/artifact repositories and system directories for files outside expected repository structures, particularly in parent directories or /tmp
    Affected if Files exist outside the designated repository paths or in system directories that should not contain uploaded artifacts

You are affected if Artifactory version is below 7.76.2 AND the system has authenticated users with upload permissions, regardless of whether exploitation has occurred yet.

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 7.76.2 or later
Fixed in 7.76.2
Interim mitigation

Upgrade JFrog Artifactory to version 7.76.2 or later to remediate the insufficient artifact validation. Prior to upgrade, restrict administrative access and monitor for suspicious artifact upload patterns.

Recommended fix High confidence

Artifactory 7.76.2 or later

  1. 1. Review the JFrog Artifactory upgrade guide at https://jfrog.com/help/r/artifactory-upgrade
  2. 2. Back up your current Artifactory installation including the $ARTIFACTORY_HOME directory and database
  3. 3. Ensure you have a rollback plan in case of issues
  4. 4. Download Artifactory version 7.76.2 or later from the JFrog download center
  5. 5. Stop the Artifactory service
  6. 6. Run the upgrade installer for your platform (RPM/DEB for Linux, Windows installer, or Docker/Helm for containerized deployments)
  7. 7. Start the Artifactory service
  8. 8. Verify the upgrade was successful by checking the version in the UI (Administration > System Info) or via the REST API
Caveat Review JFrog's release notes for 7.76.x for any configuration or feature changes that may affect your deployment

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

Fix this in Artifactory Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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