How severe is CVE-2020-2254?

CVE-2020-2254 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-2254?

CVE-2020-2254 affects the following packages: io.jenkins.blueocean:blueocean (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2254?

Update io.jenkins.blueocean:blueocean to 1.23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2254 is resolved across your whole dependency graph.

How do I detect CVE-2020-2254 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.blueocean:blueocean, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-2254 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2020-2254 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-2254 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-2254?

CVE-2020-2254 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-2254?

CVE-2020-2254 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2020-2254 published, and has it been updated?

CVE-2020-2254 was published on September 16, 2020 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-2254 — blueocean

MEDIUMFix: jenkinsci/blueocean-plugin@f0dd4b6

CVE-2020-2254 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in io.jenkins.blueocean:blueocean. A fix is available for io.jenkins.blueocean:blueocean — see the affected versions and patch details below.

Path traversal vulnerability in Blue Ocean Plugin

Also known asGHSA-vq7j-6pcq-f48p

Published

Sep 16, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕io.jenkins.blueocean:blueocean

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Blue Ocean Plugin 1.23.2 and earlier provides an undocumented feature flag, blueocean.features.GIT_READ_SAVE_TYPE, that when set to the value clone allows an attacker with Item/Configure or Item/Create permission to read arbitrary files on the Jenkins controller file system.

Blue Ocean Plugin 1.23.3 no longer includes this feature and redirects existing usage to a safer alternative.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.blueocean:blueocean`	all versions	1.23.3`io.jenkins.blueocean:blueocean:1.23.3`

Affected Products

1 product · 1 configurations

Application

blue oceanjenkins

≤ 1.23.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.blueocean:blueocean, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.blueocean:blueocean to 1.23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2254 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`jenkins-2-plugins-0:3.11.1603460090-1.el7`	RHSA-2020:5102
Red Hat OpenShift Container Platform 4.6	`jenkins-2-plugins-0:4.6.1601368321-1.el8`	RHSA-2020:4297

Frequently Asked Questions

Blue Ocean Plugin 1.23.2 and earlier provides an undocumented feature flag, `blueocean.features.GIT_READ_SAVE_TYPE`, that when set to the value `clone` allows an attacker with Item/Configure or Item/Create permission to read arbitrary files on the Jenkins controller file system. Blue Ocean Plugin 1.23.3 no longer includes this feature and redirects existing usage to a safer alternative.

O3 Security · Impact-Aware SCA

Is CVE-2020-2254 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-22Path Traversal

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

blueocean-plugin

4.5/10

Code-Review3/10

Maintained3/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Sep 16, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2254

GHSA-vq7j-6pcq-f48p

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 09 16 Advisorynvd.nist.gov · CVE 2020 2254 Webgithub.com · f0dd4b68d62ac3c3c85012d6eb0c92bcebf85e12 Packagegithub.com · blueocean plugin

Related vulnerabilities

Also affects blueocean

This CVE is medium severity; 7 of 7 other CVEs affecting blueocean are rated as high or higher (top: high).

CVE-2023-40341CVE-2020-2255CVE-2019-1003013CVE-2017-1000105CVE-2017-1000106CVE-2019-1003012CVE-2017-1000110

Same weakness: CWE-22

This CVE is medium severity; 1 of 1 other CVE with CWE-22 is rated as high or higher (top: high).

CVE-2026-62331Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2254 — blueocean

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2020-2254 in your dependencies?