dbcve.org
ArtifactoryApplication · Jfrog

CVE-2019-17444

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-12
Fix available
A fix is available. Upgrade to 6.17.0 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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 uses default passwords (such as "password") for administrative accounts and does not require users to change them. This may allow unauthorized network-based attackers to completely compromise of Jfrog Artifactory. This issue affects Jfrog Artifactory versions prior to 6.17.0.

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 ships with default administrative passwords (such as 'password') that are not forced to be changed during initial setup. This allows remote attackers with network access to authenticate as administrators using these known default credentials, achieving full compromise of the Artifactory instance.

MitigationUpgrade to Jfrog Artifactory 6.17.0 or later, and immediately change all default administrative passwords to strong, unique credentials.

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:< 6.17.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Artifactory installation and version
    Check the installed version by querying the Artifactory REST API endpoint /api/system/version, or inspect the $ARTIFACTORY_HOME/etc/info/artifactory.system.xml file, or run 'artifactoryctl version' if available
    Affected if The detected version is lower than 6.17.0
  2. Check if default admin account exists
    Query the users endpoint via REST API (GET /api/security/users) or inspect the $ARTIFACTORY_HOME/etc/artifactory-users.xml file to enumerate admin-level accounts
    Affected if An admin user with the username 'admin' exists in the system
  3. Verify default password status
    Attempt to authenticate to Artifactory using the REST API with credentials admin:password, or inspect the $ARTIFACTORY_HOME/etc/security/ directory for password configuration files
    Affected if Authentication succeeds with the default password 'password' or other known default passwords
  4. Check password change enforcement
    Review Artifactory access logs ($ARTIFACTORY_HOME/logs/access.log) for any 'first login' or 'password reset' flag, or check the security.xml configuration for password policy settings
    Affected if No password change was forced during initial setup or the default password remains active

You are affected if Artifactory version is below 6.17.0 AND the default administrative account still uses a default password that has not been changed from the factory setting.

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

Upgrade to Jfrog Artifactory 6.17.0 or later, and immediately change all default administrative passwords to strong, unique credentials.

Recommended fix High confidence

6.17.0

  1. Back up your current Artifactory installation and database before upgrading
  2. Stop the Artifactory service
  3. Upgrade Artifactory to version 6.17.0 or later following the official upgrade documentation
  4. Start the Artifactory service
  5. After upgrade, log in to the admin console and immediately change the default password for the admin account to a strong, unique password
  6. Verify that default passwords are no longer in use and the upgrade was successful
  7. Review all user accounts to ensure they have strong, unique passwords
Caveat Review JFrog's upgrade guide for any migration requirements between your current version and 6.17.0, as database migration or configuration changes may be needed

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

Fix this in Artifactory Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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