Skip to content
Fencer Intel
high 7.5

CVE-2019-14993 json

Istio ReDoS Vulnerability

published 7y ago modified last mo. also GHSA-qcvw-82hh-gq38 , EUVD-2022-4952

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

Istio before 1.1.13 and 1.2.x before 1.2.4 mishandles regular expressions for long URIs, leading to a denial of service during use of the JWT, VirtualService, HTTPAPISpecBinding, or QuotaSpecBinding API.

Patch / fix

  • go istio.io/istio 1.1.13, 1.2.4
  • istio istio 1.1.13, 1.2.4
  • ior service mesh 1.1 1.1.0-3.el8
  • kiali service mesh 1.1 v1.12.7.redhat1-1.el7
  • servicemesh service mesh 1.1 1.1.0-5.el8
  • servicemesh-cni service mesh 1.1 1.1.0-3.el8
  • servicemesh-mixc service mesh 1.1 1.1.0-5.el8
  • servicemesh-mixs service mesh 1.1 1.1.0-5.el8
  • servicemesh-proxy service mesh 1.1 1.1.0-4.el8
  • servicemesh-galley service mesh 1.1 1.1.0-5.el8

red hat advisories RHEA-2020:1416

Is CVE-2019-14993 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-14993 updated cvss 7.5

istio/envoy: mishandling regular expressions for long URIs leading to DoS

  • Red Hat OpenShift Service Mesh 1.1 ior 1.1.0-3.el8, servicemesh 1.1.0-5.el8, servicemesh-cni 1.1.0-3.el8, servicemesh-mixc 1.1.0-5.el8, servicemesh-mixs 1.1.0-5.el8, servicemesh-proxy 1.1.0-4.el8, +10 more Red Hat OpenShift Service Mesh 1.1 kiali v1.12.7.redhat1-1.el7
    fixed: vendor fix RHEA-2020:1416

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

2.28% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/issues/7728 referenced PoC, tagged "exploit" by a source, unverified
  • gcc.gnu.org https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86164 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go istio.io/istio
<1.1.13
>=1.2.0, <1.2.4
1.1.13
1.2.4

Classification

Weakness
  • CWE-185 Incorrect Regular Expression

References

Sources

Fencer Intel 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.