CVE-2019-10753: Incorrect Resource Transfer Between Spheres in eclipse-wtp

Summary

11/09/2019
Yes i
Moderate
5.9

CVE-2019-10753: Incorrect Resource Transfer Between Spheres in eclipse-wtp. Affects com.diffplug.spotless:spotless-eclipse-wtp versions < 3.9.6. Fixed in 3.9.6. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package under scrutiny is com.diffplug.spotless:spotless-eclipse-wtp, which is a Maven package. It is a tool used for resolving dependencies in Eclipse projects. The package is vulnerable to an insecure channel issue, where dependencies are resolved over an insecure connection (http). This vulnerability affects versions prior to 3.9.6 for eclipse-wtp, prior to 9.4.4 for eclipse-cdt, and prior to 3.0.1 for eclipse-groovy. The Spotless tool is used during the build process, and if the build occurs over an insecure connection, a malicious user could perform a Man-in-the-Middle attack and alter the build artifacts. This could lead to compromised artifacts and potential alteration of developers' systems.

Vulnerability Detail

The vulnerability arises from the insecure channel used for dependency resolution during the build process. If the build occurs over an insecure connection, a malicious user can intercept the communication and modify the build artifacts. This can lead to compromised artifacts being used by developers, potentially resulting in altered systems. The probability of this vulnerability being exploited is low, but until the artifacts are validated as unaltered, there is a risk of compromise.

How To Fix

Latest published version: 3.23.0 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.9.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

In conclusion, the com.diffplug.spotless:spotless-eclipse-wtp package is vulnerable to an insecure channel issue during dependency resolution. This can lead to compromised build artifacts and potential alteration of developers' systems. It is recommended to update to the fixed versions of the affected packages to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.diffplug.spotless:spotless-eclipse-wtp →

Share this vulnerability

FAQ

The impact of this vulnerability is that a malicious user can alter the build artifacts during the build process. If developers use these compromised artifacts, their systems could be altered.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using just the pom.xml file.

The CVSS score of this vulnerability is 5.9.

No, there is no specific workaround mentioned for this vulnerability. It is recommended to update to the fixed versions of the affected packages.

To ensure that the artifacts were not compromised, the maintainer of the package needs to confirm that none of the artifacts published to the registry were altered. Until this confirmation is obtained, there is a possibility of compromise.

How To Fix

Latest published version: 3.23.0 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.9.6

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback