dbcve.org
Storable ConfigsApplication · Jenkins

CVE-2020-2277

MEDIUM · 6.5 CVSS v3.1 Published 2020-09-16
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Jenkins Storable Configs Plugin 1.0 and earlier allows users with Job/Read permission to read arbitrary files on the Jenkins controller.

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 confidence

The Jenkins Storable Configs Plugin versions 1.0 and earlier contains an arbitrary file read vulnerability. Users with only Job/Read permission (a low-privilege Jenkins role) can read any file on the Jenkins controller file system, potentially exposing sensitive configuration files, credentials, SSH keys, or other system files.

MitigationUpgrade to a patched version of the Storable Configs Plugin; if no patched version is available, remove or disable the plugin. Review file system permissions and rotate any credentials that may have been exposed.

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
Affected:<= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Storable Configs Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Storable Configs'. Alternatively, check if the file $JENKINS_HOME/plugins/storable-configs.jpi (or .hpi) exists.
    Affected if The plugin file exists in the plugins directory or is listed in the installed plugins table.
  2. Check the installed plugin version
    In the Installed Plugins table, find the version listed for 'Storable Configs'. If using CLI, run: jenkins-cli.jar groovy = println jenkins.pluginManager.getPlugin('storable-configs').version
    Affected if The version is 1.0 or any version earlier than 1.0.
  3. Confirm the plugin is active and loaded
    In Manage Jenkins > Manage Plugins > Instable tab, ensure Storable Configs is not marked as 'Disabled'. Check the plugin is listed as active in the runtime.
    Affected if The plugin is installed and not explicitly disabled.

If the Storable Configs Plugin is installed, enabled, and its version is 1.0 or earlier, then your environment is affected by this arbitrary file read vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Upgrade to a patched version of the Storable Configs Plugin; if no patched version is available, remove or disable the plugin. Review file system permissions and rotate any credentials that may have been exposed.

Fix this in Storable Configs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2277 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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