Skip to content

fabric8-maven-plugin: insecure way to construct Yaml Object leading to remote code execution

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Feb 29, 2024

Package

maven io.fabric8:fabric8-maven-plugin (Maven)

Affected versions

>= 4.0.0-M1, <= 4.4.2

Patched versions

None

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

References

Published by the National Vulnerability Database Oct 22, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Feb 29, 2024
Last updated Feb 29, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2020-10721

GHSA ID

GHSA-w7gj-h6f2-x4c6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.