Skip to content
Fencer Intel
critical 9.8

CVE-2019-9733 in the critical feed json

An issue was discovered in JFrog Artifactory 6.7.3.

published 7y ago modified 4mo ago also EUVD-2019-19098

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
53.9%
EPSS 53.9% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known, plus a Nuclei check

Summary

An issue was discovered in JFrog Artifactory 6.7.3. By default, the access-admin account is used to reset the password of the admin account in case an administrator gets locked out from the Artifactory console. This is only allowable from a connection directly from localhost, but providing a X-Forwarded-For HTTP header to the request allows an unauthenticated user to login with the default credentials of the access-admin account while bypassing the whitelist of allowed IP addresses. The access-admin account can use Artifactory's API to request authentication tokens for all users including the admin account and, in turn, assume full control of all artifacts and repositories managed by Artifactory.

Is CVE-2019-9733 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

53.88% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template JFrog Artifactory 6.7.3 - Admin Login Bypass nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/152172/JFrog-Artifactory-Administrator-Authentication-Bypass.html referenced PoC, tagged "exploit" by a source, unverified
  • ciphertechs.com https://www.ciphertechs.com/jfrog-artifactory-advisory/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.