Storage ConfigsApplication · Jenkins
CVE-2022-30972
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 (CSRF) vulnerability in Jenkins Storable Configs Plugin 1.0 and earlier allows attackers to have Jenkins parse a local XML file (e.g., archived artifacts) that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.
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 Storable Configs Plugin 1.0 and earlier allows attackers to trick Jenkins into parsing malicious XML files containing external entity references. This XXE (XML External Entity) injection enables extraction of secrets from the Jenkins controller filesystem and SSRF attacks against internal services.
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
Storage ConfigsApplication
<= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Storable Configs plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or list plugins via Jenkins CLI: jenkins-cli.jar or REST API at /pluginManager/api/json?tree=plugins[shortName,version]Affected if The Storable Configs plugin appears in the installed plugins list
-
Check installed plugin versionIn the Manage Plugins > Installed view, find the 'Storable Configs' or 'storage-configs' entry and note the version number shownAffected if Version is 1.0 or earlier (the vulnerable version range)
-
Verify if plugin configuration parsing is activeCheck Jenkins job configurations or system configuration pages for usage of the Storable Configs feature, which allows storing configuration as XML files that Jenkins will parseAffected if The plugin is actively configured to parse XML files containing user-supplied or externally sourced content
-
Confirm XML parser allows external entitiesReview any custom XML configuration files being processed by the plugin for doctype declarations containing 'ENTITY' definitions, or inspect network logs for outbound requests triggered by XXE payloadsAffected if Jenkins controller makes outbound network requests or reads local files based on XML entity references in parsed configuration content
You are affected if the Storable Configs plugin version 1.0 or earlier is installed and is being used to parse XML configuration files that could contain malicious external entity references.
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 Jenkins Storable Configs Plugin to version 1.1 or later, which adds CSRF protection (crumb validation) and properly configures XML parsers to disable external entity processing.
Fix this in Storage Configs
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30972 — 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-30972 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