An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.

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.

A user with JFrog Artifactory Cargo remote repository read access could make Artifactory request unintended URLs and return the response.

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).

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.

An authenticated privilege-escalation vulnerability in JFrog Platform may be exploited under admin-provisioned account conditions. Successful exploitation may grant temporary platform administrator access.

A URL validation weakness in JFrog Artifactory Ansible repository handling could allow a user, under specific repository access conditions, to cause unintended server-side requests. The issue primarily affects confidentiality and integrity and has been addressed in fixed Artifactory versions.

A path validation weakness in archive extraction/write handling allows entries with traversal sequences to be written outside the intended build artifacts location.

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.

Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.

An unauthenticated attacker may cause untrusted package content to be cached under specific conditions, potentially affecting artifact integrity and availability.

An authenticated user without repository read permission may access package metadata under specific conditions.

JFrog Artifactory contains an authentication weakness that, under default configuration, may allow an unauthenticated attacker with network access to obtain administrative privileges.

A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions.

Credentials for a deleted user may remain valid for a short period under specific conditions.

An unauthenticated user may access restricted repository information under specific conditions.

An authenticated user without repository read permission may access private NuGet metadata under specific conditions.

An authenticated user may view private Puppet module metadata without repository read access.

An authenticated user without repository read permission may access private OCI referrer metadata under specific conditions.

A repository reader with cache-deploy permission may access content outside a configured upstream path under specific conditions.

An authenticated user may write files outside the intended Artifactory work directory under specific conditions.

An unauthenticated user may access restricted Artifactory content when a credentialed remote repository is configured in a specific way.

A repository publisher without delete permission may modify protected package content under specific conditions.

A bundle writer may create misleading release promotion information under specific conditions.

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.