Skip to content
Fencer Vulns
high 8.1

CVE-2019-10249 json

Potentially compromised builds

published 2019-05-06 7 y ago modified 2026-06-17 4 mo ago also GHSA-rfj2-4g26-7jw5 , EUVD-2022-5161

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

All Xtext & Xtend versions prior to 2.18.0 were built using HTTP instead of HTTPS file transfer and thus the built artifacts may have been compromised.

Patch / fix

  • maven org.eclipse.xtext:org.eclipse.xtext 2.18.0
  • maven org.eclipse.xtend:org.eclipse.xtend.core 2.18.0
  • The Eclipse Foundation Eclipse Xtext 2.18.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-10249 updated cvss 5.3

eclipse-xtext: insecure build using HTTP instead of HTTPS leading to possibly compromised built artifacts

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/eclipse/xtext-xtend/issues/759 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.eclipse.xtext:org.eclipse.xtext
<2.18.0
2.18.0
maven org.eclipse.xtend:org.eclipse.xtend.core
<2.18.0
2.18.0

Affected products

  • The Eclipse Foundation Eclipse Xtext

Classification

Weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere
  • CWE-494 Download of Code Without Integrity Check
  • CWE-116 Improper Encoding or Escaping of Output
  • CWE-319 Cleartext Transmission of Sensitive Information

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.