Eclipse Wtp
Approved changes feed: RSS · Atom
cpe:2.3:a:diffplug:eclipse-wtp:*:*:*:*:*:spotless:*:*
part: a version: * update: *
| Vendor | Diffplug (04a46f2f-b2f7-515a-8d64-70a007f0e092) |
|---|---|
| Product | Eclipse Wtp (a95a2d06-48cc-593d-bfeb-9231b582d268) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | spotless |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-10753 |
vulnerable | 2026-06-08 05:12:25.230373 |
Details available
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.
Published: 2019-09-05T19:45:24.000Z
Updated: 2024-08-04T22:32:01.979Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.