JenkinsApplication
CVE-2024-43045
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 2.470 and earlier, LTS 2.452.3 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to access other users' "My Views".
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 confidenceJenkins versions 2.470 and earlier, LTS 2.452.3 and earlier lack a permission check in an HTTP endpoint handling 'My Views'. Users with only Overall/Read permission can access other users' private 'My Views' configurations, exposing potentially sensitive dashboard customizations and information about what jobs other users are monitoring.
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
JenkinsApplication
< 2.452.4< 2.471CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Check Jenkins versionNavigate to Manage Jenkins > About Jenkins or access /api/json?tree=version to retrieve the installed version numberAffected if Version is 2.470 or earlier, or LTS 2.452.3 or earlier
-
Identify if My Views feature is in useCheck if any users have created private views under the 'My Views' section in Jenkins. Navigate to a user's My Views or query the API endpoint /user/{user}/my-views/ to see if private views existAffected if My Views feature is being used and contains private view configurations for any user
-
Verify authorization configurationNavigate to Manage Jenkins > Security > Authorization or inspect the authorization matrix in jenkins.model.Jenkins.authorizationStrategy. Check if 'Overall/Read' permission is granted to any user or group that should not have visibility into other users' private viewsAffected if Users or groups with Overall/Read permission exist alongside private My Views configurations belonging to other users
You are affected if running Jenkins version 2.470 or earlier (or LTS 2.452.3 or earlier) AND the My Views feature is in use with private configurations accessible to users who should not see them.
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.
dbcve · scoped2.452.42.471
Upgrade to Jenkins 2.471 or LTS 2.452.4 or later, which implements proper authorization checks for the affected HTTP endpoint.
Jenkins LTS 2.452.4 or later, or Jenkins 2.471 or later
- 1. Backup the Jenkins JENKINS_HOME directory, including all configurations, jobs, and user data
- 2. Review the Jenkins 2.452.4 (LTS) or 2.471 (weekly) release notes for any migration notes or breaking changes
- 3. Download the target Jenkins WAR file from the official Jenkins repository (jenkins.io)
- 4. Stop the Jenkins service
- 5. Replace the existing jenkins.war file in the Jenkins installation directory with the new version
- 6. Start the Jenkins service
- 7. Verify the upgrade was successful by logging in and confirming the version number
- 8. Verify that users with Overall/Read permission can no longer access other users' My Views (the vulnerability should be fixed)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43045 — 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-43045 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