Filtered by vendor Jfrog
Subscribe
Search
Total
5 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2019-17444 | 1 Jfrog | 1 Artifactory | 2020-10-20 | 7.5 HIGH | 9.8 CRITICAL |
| 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. | |||||
| CVE-2018-19971 | 1 Jfrog | 1 Artifactory | 2020-08-24 | 7.5 HIGH | 9.8 CRITICAL |
| JFrog Artifactory Pro 6.5.9 has Incorrect Access Control. | |||||
| CVE-2019-9733 | 1 Jfrog | 1 Artifactory | 2020-08-24 | 7.5 HIGH | 9.8 CRITICAL |
| 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. | |||||
| CVE-2016-10036 | 1 Jfrog | 1 Artifactory | 2018-06-13 | 7.5 HIGH | 9.8 CRITICAL |
| Unrestricted file upload vulnerability in ui/artifact/upload in JFrog Artifactory before 4.16 allows remote attackers to (1) deploy an arbitrary servlet application and execute arbitrary code by uploading a war file or (2) possibly write to arbitrary files and cause a denial of service by uploading an HTML file. | |||||
| CVE-2016-6501 | 1 Jfrog | 1 Artifactory | 2016-12-15 | 7.5 HIGH | 9.8 CRITICAL |
| JFrog Artifactory before 4.11 allows remote attackers to execute arbitrary code via an LDAP attribute with a crafted serialized Java object, aka LDAP entry poisoning. | |||||