CVE-2020-2278 json
Arbitrary file write vulnerability in Jenkins Storable Configs Plugin
published 6y ago modified 4mo ago also GHSA-qv6q-4jwx-7j5c , EUVD-2022-5033
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Jenkins Storable Configs Plugin 1.0 and earlier does not restrict the user-specified file name, allowing attackers with Job/Configure permission to replace any other '.xml' file on the Jenkins controller with a job config.xml file's content.
Is CVE-2020-2278 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jvnet.hudson.plugins:storable-configs-plugin | <=1.0 |
no fix listed |
Affected products
- Jenkins project Jenkins Storable Configs Plugin
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
- jenkins.io /security/advisory/2020-09-16/#SECURITY-1968%20%282%29
-
openwall.com
/lists/oss-security/2020/09/16/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-2278
advisory
-
github.com
/jenkinsci/storable-configs-plugin
package
-
jenkins.io
/security/advisory/2020-09-16/#SECURITY-1968%20(2)
web
Sources
- CVE List CVE-2020-2278
- GitHub Advisory GHSA-qv6q-4jwx-7j5c
- NVD CVE-2020-2278
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.