Authorize ProjectApplication · Jenkins
CVE-2024-52552
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 · uneditedJenkins Authorize Project Plugin 1.7.2 and earlier evaluates a string containing the job name with JavaScript on the Authorization view, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
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 confidenceThe Jenkins Authorize Project Plugin versions 1.7.2 and earlier contain a stored cross-site scripting (XSS) vulnerability where the job name is improperly evaluated with JavaScript on the Authorization view. Attackers with Item/Configure permission can inject malicious scripts that execute when other users access the Authorization configuration page.
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
Authorize ProjectApplication
<= 1.7.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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Authorize Project plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Authorize Project' in the list. Alternatively, check the plugin directory (JENKINS_HOME/plugins/) for the authorize-project folder.Affected if The plugin folder exists or the plugin appears in the installed list.
-
Check the installed plugin versionIn Manage Plugins > Installed tab, find Authorize Project and note the Version column. Or examine the file JENKINS_HOME/plugins/authorize-project/META-INF/MANIFEST.MF for the Implementation-Version attribute.Affected if The version is 1.7.2 or earlier.
-
Confirm users have Item/Configure permissionNavigate to Manage Jenkins > Manage Users and review which users or groups have Item/Configure (or Item/ExtendedRead) permissions. Check configured security realms and authorization matrices in Configure Global Security.Affected if Untrusted or unknown users have Item/Configure permission.
-
Inspect job names for suspicious contentReview job configuration files in JENKINS_HOME/jobs/*/config.xml or via Jenkins UI at each job's Configure page. Look for unusual script tags, event handlers (onerror, onload), or encoded JavaScript in the job name field.Affected if Any job name contains <script>, javascript:, or HTML event handlers like onerror/onload.
A user is affected if the Authorize Project plugin version is 1.7.2 or earlier AND untrusted users have Item/Configure permission, allowing injection of malicious job names that execute when the Authorization view is accessed.
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 the Authorize Project Plugin to version 1.7.3 or later which addresses the improper handling of job names. As an immediate workaround, restrict Item/Configure permission to trusted users only.
Fix this in Authorize Project
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52552 — 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-2024-52552 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