Storable ConfigsApplication · Jenkins
CVE-2022-30971
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 Storable Configs Plugin 1.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
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 Storable Configs Plugin versions 1.0 and earlier contains an XML external entity (XXE) vulnerability due to its XML parser not being configured to disable external entity processing. This allows attackers to inject malicious XML containing external entity references to read local files or perform server-side request forgery (SSRF) attacks.
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
Storable 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Storable Configs Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and search for 'Storable Configs', or check the plugin directory on the Jenkins controller filesystem for the storable-configs plugin files.Affected if The plugin appears in the list of installed plugins.
-
Check installed plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed, find Storable Configs, and note the version column. Alternatively, examine the plugin's .hpi file in the plugins directory for the manifest containing the version.Affected if The version is 1.0 or earlier.
-
Identify XML configuration files processed by the pluginSearch the Jenkins job configurations and any custom config files for references to 'storable-configs' or 'storable' XML functionality. Check job config.xml files and any stored configuration files that the plugin may process.Affected if XML configuration files associated with the Storable Configs Plugin exist in the Jenkins environment.
-
Check plugin XML parser configurationExamine the plugin's configuration files or Java source code (if accessible) to determine if the XML parser has external entity processing disabled. Look for XMLInputFactory, DocumentBuilder, or SAXParser configurations.Affected if The plugin configuration does not explicitly disable external entity processing (XXE protection is not present).
A user is affected if the Storable Configs Plugin version 1.0 or earlier is installed and any XML configuration files are processed by this plugin without explicit XXE protection in the parser settings.
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 Storable Configs Plugin version 1.1 or later, which properly configures the XML parser to prevent XXE attacks by disabling external entity processing.
Fix this in Storable Configs
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30971 — 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-30971 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