Job Configuration HistoryApplication · Jenkins
CVE-2023-41932
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 Job Configuration History Plugin 1227.v7a_79fc4dc01f and earlier does not restrict 'timestamp' query parameters in multiple endpoints, allowing attackers with to delete attacker-specified directories on the Jenkins controller file system as long as they contain a file called 'history.xml'.
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 · moderate confidenceThe Jenkins Job Configuration History Plugin versions 1227.v7a_79fc4dc01f and earlier fails to properly validate 'timestamp' query parameters in multiple API endpoints. This allows authenticated attackers to perform path traversal and delete arbitrary directories on the Jenkins controller filesystem, with the constraint that the targeted directories must contain a file named 'history.xml'.
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
Job Configuration HistoryApplication
<= 1227.v7a_79fc4dc01fCVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Verify Job Configuration History plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Job Configuration History', or run: jenkins.model.Jenkins.getInstance().getPluginManager().getPlugin('job-configuration-history')Affected if The plugin is not found in the installed plugins list, meaning this CVE does not apply.
-
Check the installed plugin versionIn the plugin manager, view the version column for Job Configuration History Plugin, or run: jenkins.model.Jenkins.getInstance().getPluginManager().getPlugin('job-configuration-history').getVersion()Affected if The installed version is 1227.v7a_79fc4dc01f or earlier.
-
Confirm the plugin is active and enabledNavigate to Manage Jenkins > Configure System > Job Configuration History and verify the plugin configuration page loads, or check that the plugin is not disabled in jenkins.xml or configuration.Affected if The plugin is enabled and accessible, making it a potential attack surface.
-
Identify users with job configuration history API accessReview Jenkins authorization matrix or role-based access control settings for users or groups with Job/Configure or JobConfigurationHistory permissions, or inspect: jenkins.model.Jenkins.instance.getAuthorizationStrategy()Affected if Any authenticated users or groups have permissions that would allow them to access the affected API endpoints.
You are affected if the Job Configuration History plugin is installed with version 1227.v7a_79fc4dc01f or earlier and is enabled, allowing authenticated users to potentially exploit the path traversal vulnerability via timestamp query parameters.
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 Job Configuration History Plugin version 1228.v5e7f8ed409e1 or later. If immediate upgrading is not feasible, restrict access to the affected plugin endpoints using Jenkins' authorization mechanisms.
Fix this in Job Configuration History
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41932 — 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-2023-41932 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