| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A party with write access to stored session data may affect JFrog Artifactory under specific conditions. |
| A user with access to a valid SAML response may impersonate another user under specific conditions. |
| An unauthenticated user may bypass authentication under specific cache conditions. |
| A low-privileged authenticated user may access restricted support information under specific conditions. |
| A holder of a valid integration credential may impersonate other users under specific conditions. |
| An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions. |
| A user who can read an existing remote VCS repository can replace its configured origin or supply an absolute VCS data URL. |
| An authorization weakness in JFrog Artifactory Composer repository handling may allow an authenticated user, under specific conditions, to read package metadata from repositories they are not authorized to read. The issue affects confidentiality and has been addressed in fixed Artifactory versions. |
| Under specific circumstances, low-level user can run request to remote CocoaPods repos via JFrog Artifactory External Dependency. |
| An authenticated user may initiate repository migration operations without required repository permissions, potentially causing information disclosure, unauthorized state changes, and service disruption. Fixed versions address the issue. |
| 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. |
| 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). |
