ArtifactoryApplication · Jfrog
CVE-2019-10324
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA CSRF vulnerability in Jenkins Artifactory Plugin versions 3.2.2 and earlier allowed attackers to trick authenticated users into performing unintended actions including scheduling release builds, staging Gradle/Maven releases, and promoting builds via multiple endpoints (ReleaseAction#doSubmit, GradleReleaseApiAction#doStaging, MavenReleaseApiAction#doStaging, UnifiedPromoteBuildAction#doSubmit) that lacked proper CSRF token validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ArtifactoryApplication
<= 3.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Artifactory Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or run: jenkins-cli.jar who-am-i (if available), or inspect $JENKINS_HOME/plugins for artifactory directoryAffected if The artifactory plugin directory exists in the Jenkins plugins folder
-
Determine the installed Artifactory Plugin versionIn Jenkins UI: Manage Jenkins > Manage Plugins > Installed > Artifactory Plugin > Version column. Or inspect $JENKINS_HOME/plugins/artifactory/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if The version listed is 3.2.2 or earlier (any version <= 3.2.2)
-
Verify if authenticated users have access to release/build promotion endpointsCheck if any users have permissions for: 1) Release builds (ReleaseAction), 2) Gradle staging (GradleReleaseApiAction), 3) Maven staging (MavenReleaseApiAction), 4) Build promotion (UnifiedPromoteBuildAction). Review job configurations and user permissions in Manage Jenkins > Manage and Assign RolesAffected if Any authenticated users (including users with job-specific permissions) can access the release or promotion features of Artifactory-integrated jobs
-
Confirm CSRF protection status in JenkinsNavigate to Manage Jenkins > Configure Global Security > CSRF Protection section. Verify if either Default Crumb Issuer or Custom Crumb Issuer is enabledAffected if CSRF protection is disabled entirely (Exposed API tokens mode selected without crumb validation)
-
Check if plugin endpoints handle CSRF tokensReview HTTP responses from the affected endpoints: ReleaseAction/doSubmit, GradleReleaseApiAction/doStaging, MavenReleaseApiAction/doStaging, UnifiedPromoteBuildAction/doSubmit. Submit a request with an invalid or missingcrumb token and observe if it is rejectedAffected if Requests to these endpoints succeed without a valid CSRF crumb token (the plugin does not validate crumbs on these endpoints)
You are affected if the Artifactory Plugin version is 3.2.2 or earlier AND authenticated users have access to release/build promotion features AND CSRF protection is either disabled or the plugin does not validate CSRF tokens on the vulnerable endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Jenkins Artifactory Plugin version 3.3.0 or later which includes CSRF protection, or ensure Jenkins' global CSRF protection (crumb validation) is enabled and the plugin properly validates CSRF tokens on these endpoints.
Fix this in Artifactory
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10324 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data