Skip to content
Fencer Intel
high 7.5

CVE-2019-12243 json

Istio may not check inbound TCP connections against istio-policy

published 7y ago modified 4mo ago also GHSA-6g5f-f5pm-mjrg , EUVD-2022-0859

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

Summary

Istio 1.1.x through 1.1.6 has Incorrect Access Control.

Patch / fix

  • go istio.io/istio 1.1.7

Is CVE-2019-12243 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

Exploit prediction

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

Exploits and checks

  • istio.io https://istio.io/blog/2019/cve-2019-12243/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.4 AV:A/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 9.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/E:H/RL:O/RC:C

Affected packages

ecosystem package affected fixed in
go istio.io/istio
>=1.1.0, <1.1.7
1.1.7

Classification

Weakness

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.