Threat database

A user with access to a valid SAML response may impersonate another user under specific conditions.

A party with write access to stored session data may affect JFrog Artifactory under specific conditions.

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

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

An unauthenticated user may bypass authentication under specific cache conditions.

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

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

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

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

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

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

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

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

A Project Resource Manager may gain broader administrative privileges under specific 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 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 deserialization weakness in JFrog Artifactory package handling could allow a low-privileged user to impact confidentiality, integrity, and availability under specific repository conditions.

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 user with JFrog Artifactory Cargo remote repository read access could make Artifactory request unintended URLs and return the response.

Incorrect authorization validation in refresh token signature allows non-admin users to obtain a signed JFrog administrator token.