Fabric8 MavenApplication · Redhat
CVE-2020-10721
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 · uneditedA 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.
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 confidenceThe fabric8-maven-plugin versions 4.0.0 and later contain a deserialization vulnerability when processing wildfly-swarm or thorntail YAML configuration files. A malicious YAML file on the local machine can be crafted to deserialize untrusted data, enabling arbitrary code execution during the Maven build process.
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
Fabric8 MavenApplication
>= 4.0.0, <= 4.4.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Locate fabric8-maven-plugin versionInspect your project's pom.xml for the fabric8-maven-plugin dependency or plugin declaration, or check your local Maven repository (typically ~/.m2/repository/io/fabric8/fabric8-maven-plugin/) for the installed version numberAffected if The version falls within 4.0.0 to 4.4.1 inclusive
-
Identify wildfly-swarm or thorntail usageSearch your project for references to 'wildfly-swarm' or 'thorntail' in pom.xml dependencies, YAML configuration files, or project documentationAffected if Your project uses wildfly-swarm or thorntail dependencies or configuration
-
Find YAML configuration filesLocate any .yml or .yaml files in your project that contain wildfly-swarm or thorntail specific configuration (such as project-defaults.yml or similar)Affected if YAML configuration files for wildfly-swarm or thorntail are present in the project
-
Verify plugin configuration in pom.xmlExamine your pom.xml for a <plugin> entry with <artifactId>fabric8-maven-plugin</artifactId> and check if it includes configuration for thorntail or wildfly-swarm specific generators or enrichersAffected if The fabric8-maven-plugin is configured with wildfly-swarm or thorntail-specific generators or enrichers
You are affected if your fabric8-maven-plugin version is between 4.0.0 and 4.4.1 AND your project processes wildfly-swarm or thorntail YAML configuration files during the Maven build
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 dataAvoid using untrusted or modified YAML configuration files with wildfly-swarm or thorntail configurations; upgrade to a patched version of fabric8-maven-plugin when available; implement YAML input validation and consider disabling these custom configuration features if not required.
Fix this in Fabric8 Maven
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10721 — 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-2020-10721 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