Skip to content

Incorrect Resource Transfer Between Spheres in eclipse-wtp

Moderate severity GitHub Reviewed Published Sep 11, 2019 to the GitHub Advisory Database • Updated Jan 28, 2023

Package

maven com.diffplug.spotless:spotless-eclipse-cdt (Maven)

Affected versions

< 9.4.4

Patched versions

9.4.4
maven com.diffplug.spotless:spotless-eclipse-groovy (Maven)
< 3.0.1
3.0.1
maven com.diffplug.spotless:spotless-eclipse-wtp (Maven)
< 3.9.6
3.9.6

Description

In all versions prior to version 3.9.6 for eclipse-wtp, all versions prior to version 9.4.4 for eclipse-cdt, and all versions prior to version 3.0.1 for eclipse-groovy, Spotless was resolving dependencies over an insecure channel (http). If the build occurred over an insecure connection, a malicious user could have perform a Man-in-the-Middle attack during the build and alter the build artifacts that were produced. In case that any of these artifacts were compromised, any developers using these could be altered. Note: In order to validate that this artifact was not compromised, the maintainer would need to confirm that none of the artifacts published to the registry were not altered with. Until this happens, we can not guarantee that this artifact was not compromised even though the probability that this happened is low.

References

Published by the National Vulnerability Database Sep 5, 2019
Reviewed Sep 11, 2019
Published to the GitHub Advisory Database Sep 11, 2019
Last updated Jan 28, 2023

Severity

Moderate

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
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.065%
(30th percentile)

Weaknesses

CVE ID

CVE-2019-10753

GHSA ID

GHSA-gvxv-5fp2-358q

Source code

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