Job Configuration HistoryApplication · Jenkins
CVE-2022-38664
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 1165.v8cc9fd1f4597 and earlier does not escape the job name on the System Configuration History page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure job names.
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 Job Configuration History Plugin versions 1165.v8cc9fd1f4597 and earlier fail to properly escape job names on the System Configuration History page, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers with the ability to configure job names can inject malicious JavaScript that executes in the browsers of users viewing the configuration history.
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
<= 1165.v8cc9fd1f4597CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Confirm Job Configuration History plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Job Configuration History', or inspect the plugin directory (typically $JENKINS_HOME/plugins/job-configuration-history/) for the plugin manifestAffected if The plugin is present in the installed plugins list or plugin directory
-
Check installed plugin versionIn the Manage Plugins > Installed tab, locate Job Configuration History and note the version number displayed; alternatively, inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin hpi fileAffected if Version is 1165.v8cc9fd1f4597 or earlier (including any version before 1166.vd9f8ccf1b_3e2)
-
Verify System Configuration History page is accessibleAccess the System Configuration History page through Jenkins (typically at /plugin/job-configuration-history/systemConfigurationHistory/ or via Manage Jenkins > System Configuration History)Affected if The System Configuration History page loads and displays configuration history entries containing job names
-
Confirm user permission to modify job namesReview Jenkins permissions matrix (Manage Jenkins > Manage and Assign Roles) to identify users or groups with the 'Configure' permission on jobs, which allows modifying job namesAffected if Any user or group has permission to configure/create jobs and could potentially rename a job to inject malicious script
A user is affected if the Job Configuration History Plugin is installed at version 1165.v8cc9fd1f4597 or earlier and the System Configuration History page is accessible to users who could potentially view configuration history entries containing job names.
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 Jenkins Job Configuration History Plugin to version 1166.vd9f8ccf1b_3e2 or later which properly escapes job names on the System Configuration History page.
Fix this in Job Configuration History
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-2022-38664 — 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-2022-38664 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