JFrog Artifactory

A cross-site request forgery vulnerability in Jenkins Artifactory Plugin 3.2.2 and earlier in ReleaseAction#doSubmit, GradleReleaseApiAction#doStaging, MavenReleaseApiAction#doStaging, and UnifiedPromoteBuildAction#doSubmit allowed attackers to schedule a release build, perform release staging for Gradle and Maven projects, and promote previously staged builds, respectively.

JFrog Artifactory prior to version 7.28.0 and 6.23.38, is vulnerable to Broken Access Control, the copy functionality can be used by a low-privileged user to read and copy any artifact that exists in the Artifactory deployment due to improper permissions validation.

Server-Side Request Forgery (SSRF) via Terraform Remote repository

JFrog Artifactory Improper header input validation leads to email manipulation sent from the platform

JFrog Artifactory build environment properties exposure

Improper URL validation when handling specific URLs Pub, Terraform and Docker packages might lead to SSRF vulnerability

Authenticated users may access restricted Artifactory support information

Server-Side Request Forgery (SSRF) via JFrog Artifactory Cargo remote repository

Publishers without delete permission can overwrite docker layer information

JFrog Artifactory prior to version 7.29.8 and 6.23.38 is vulnerable to Reflected Cross-Site Scripting (XSS) through one of the XHR parameters in Users REST API endpoint. This issue affects: JFrog JFrog Artifactory JFrog Artifactory versions before 7.36.1 versions prior to 7.29.8; JFrog Artifactory versions before 6.23.41 versions prior to 6.23.38.

JFrog Artifactory prior to 7.31.10, is vulnerable to Broken Access Control where a Project Admin is able to create, edit and delete Repository Layouts while Repository Layouts configuration should only be available for Platform Administrators.

Potential unauthorized artifact access in JFrog Artifactory

JFrog Artifactory before 7.29.3 and 6.23.38, is vulnerable to Broken Access Control, a low-privileged user is able to delete other known users OAuth token, which will force a reauthentication on an active session or in the next UI session.

Deleted users may temporarily retain access to JFrog Artifactory

Authenticated users may write data outside the intended Docker cache path

Potential remember-me authentication bypass in JFrog Artifactory

Repository readers may access content outside configured upstream paths

Anonymous users may access restricted Artifactory repository information

Anonymous users may access restricted Artifactory content under specific configurations

A missing permission check in Jenkins Artifactory Plugin 3.2.3 and earlier in various 'fillCredentialsIdItems' methods allowed users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins.

A missing permission check in Jenkins Artifactory Plugin 3.2.2 and earlier in ArtifactoryBuilder.DescriptorImpl#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

A cross-site request forgery vulnerability in Jenkins Artifactory Plugin 3.2.2 and earlier in ArtifactoryBuilder.DescriptorImpl#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

JFrog Self-Hosted Artifactory Proxy configuration accessible to low-privilege users

Authenticated users may write files outside the intended Artifactory work directory

Authenticated users may access private OCI referrer metadata

Authenticated users may view private Puppet module metadata

Authenticated users may access private NuGet metadata

Potential unauthorized metadata exposure in JFrog Artifactory

Bundle writers may alter trusted release information in JFrog Artifactory

JFrog Artifactory before 7.31.10, is vulnerable to Broken Access Control where a project admin user is able to list all available repository names due to insufficient permission validation.