dbcve.org
ArtifactoryApplication · Jfrog

CVE-2023-42662

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 7.59.18 / 7.63.18 or later.
See remediation →
72/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 7.59 and above, but below 7.59.18, 7.63.18, 7.68.19, 7.71.8 are vulnerable to an issue whereby user interaction with specially crafted URLs could lead to exposure of user access tokens due to improper handling of the CLI / IDE browser based SSO integration.

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.59.18, 7.63.18, 7.68.19, and 7.71.8 contain an information disclosure vulnerability where specially crafted URLs in the CLI/IDE browser-based SSO integration improperly handle user access tokens, leading to token exposure.

MitigationUpgrade JFrog Artifactory to version 7.59.18, 7.63.18, 7.68.19, 7.71.8 or later to remediate this vulnerability.

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.59.0, < 7.59.18>= 7.63.5, < 7.63.18>= 7.68.7, < 7.68.19>= 7.71.2, < 7.71.8

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Check installed Artifactory version
    Access the Artifactory UI and navigate to the Administration > System > General > System Info page, or query the /api/system/version REST endpoint
    Affected if The version is 7.59.0 through 7.59.17, 7.63.5 through 7.63.17, 7.68.7 through 7.68.18, or 7.71.2 through 7.71.7
  2. Verify browser-based SSO integration is configured
    Navigate to Administration > Security > SSO in the Artifactory UI and check if any browser-based SSO provider (such as SAML, OAuth, or LDAP browser integration) is enabled
    Affected if Browser-based SSO integration is enabled and the installed version falls within the affected ranges listed above
  3. Check for token exposure in audit logs
    Review Artifactory audit logs (accessible via Administration > Analytics > Audit) for any requests containing unusually crafted URLs that may have captured access tokens, or search for log entries with pattern '/oauth2/authorization/.*token='
    Affected if Audit logs contain evidence of token exposure through specially crafted URLs and the Artifactory version is within the affected ranges

A user is affected if their JFrog Artifactory installation version falls within any of the four vulnerable ranges AND browser-based SSO integration is enabled, as the flaw requires the SSO feature to be configured.

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.59.18 / 7.63.18 / 7.68.19 or later
Fixed in 7.59.187.63.187.68.19
Interim mitigation

Upgrade JFrog Artifactory to version 7.59.18, 7.63.18, 7.68.19, 7.71.8 or later to remediate this vulnerability.

Recommended fix High confidence

7.59.18, 7.63.18, 7.68.19, or 7.71.8 (minimum)

  1. Upgrade Artifactory to version 7.59.18 or higher if currently on 7.59.x branch
  2. Alternatively, upgrade to version 7.63.18 or higher if currently on 7.63.x branch
  3. Alternatively, upgrade to version 7.68.19 or higher if currently on 7.68.x branch
  4. Alternatively, upgrade to version 7.71.8 or higher if currently on 7.71.x branch
  5. After upgrade, verify that user access tokens are no longer exposed in URL parameters
  6. Review Artifactory release notes for the chosen version for any additional changes
Caveat Check JFrog release notes for the target version for any breaking changes or migration requirements

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

Fix this in Artifactory Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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