CVE-2020-10721 — fabric8-maven-plugin
HIGHCVE-2020-10721 is a high-severity (CVSS 7.8) Deserialization of Untrusted Data vulnerability in io.fabric8:fabric8-maven-plugin. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
fabric8-maven-plugin: insecure way to construct Yaml Object leading to remote code execution
EPSS Exploitation Probability
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
io.fabric8:fabric8-maven-pluginReal-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
A flaw was found in the fabric8-maven-plugin 4.0.0 and later. When using a wildfly-swarm or thorntail custom configuration, a malicious YAML configuration file on the local machine executing the maven plug-in could allow for deserialization of untrusted data resulting in arbitrary code execution. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
The fabric8-maven-plugin has been superseded by the Eclipse project JKube and the recommendation is migrating users of the fabric8-maven-plugin to Eclipse Jkube >= 1.0.0
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.fabric8:fabric8-maven-plugin | ≥ 4.0.0-M1 | No fix |
Affected Products
fabric8-mavenredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.fabric8:fabric8-maven-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of io.fabric8:fabric8-maven-plugin for CVE-2020-10721. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2020-10721 in your dependencies?
Find it across Maven, including transitive dependencies.