| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A bundle writer may create misleading release promotion information under specific conditions. |
| An authenticated user may write files outside the intended Artifactory work directory under specific conditions. |
| An unauthenticated user may access restricted artifacts in JFrog Artifactory under specific conditions. |
| A holder of a valid integration credential may impersonate other users under specific conditions. |
| A repository reader with cache-deploy permission may access content outside a configured upstream path under specific conditions. |
| A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions. |
| An anonymous caller when anonymous access is enabled, or a low-privilege authenticated user, may learn private Release Bundle names and versions when the bundle name is known. |
| An authenticated user may view private Puppet module metadata without repository read access. |
| A repository publisher without delete permission may modify protected package content under specific conditions. |
| A party with write access to stored session data may affect JFrog Artifactory under specific conditions. |
| Improper URL validation when handling specific URLs, allows an attacker, under certain conditions, to make unauthorized requests from JFrog Artifactory, potentially exposing internal services and cached response data. |
| Incorrect authorization validation in refresh token signature allows non-admin users to obtain a signed JFrog administrator token. |
| A user with JFrog Artifactory Cargo remote repository read access could make Artifactory request unintended URLs and return the response. |
| A deserialization weakness in JFrog Artifactory package handling could allow a low-privileged user to impact confidentiality, integrity, and availability under specific repository conditions. |
| An authorization weakness in JFrog Artifactory internal metadata handling could allow a user with limited repository access to write to restricted internal metadata areas under specific conditions. Successful abuse is limited to integrity and availability impact at a low level; confidentiality is not affected. |
| JFrog Artifactory contains an authentication handling weakness in internal request processing that, under specific conditions, may allow an attacker to escalate privileges beyond the intended access level. |
| JFrog Artifactory support for Terraform remote repositories was found to be susceptible to Server-Side Request Forgery (SSRF). An authenticated user - or, if anonymous access is enabled on the repository, an unauthenticated user - could cause Artifactory to issue outbound HTTP requests to arbitrary destinations and receive the response content. |
| A path validation weakness in archive extraction/write handling allows entries with traversal sequences to be written outside the intended build artifacts location. |
| Build readers can access another repository's environment properties. A caller with read access to an ordinary repository can select a readable repository parameter while retrieving environment properties for a protected build, exposing build environment secrets (confidentiality impact; no integrity or availability impact demonstrated). |
| An authenticated privilege-escalation vulnerability in JFrog Platform may be exploited under admin-provisioned account conditions. Successful exploitation may grant temporary platform administrator access. |
