Skip to content
Fencer Intel
medium 4.3

CVE-2014-7189 json

Man-in-the-middle attack with SessionTicketsDisabled in crypto/tls

published 2014-10-07 12 y ago modified 2026-06-17 4 mo ago also GO-2021-0154 , EUVD-2014-7066

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

crpyto/tls in Go 1.1 before 1.3.2, when SessionTicketsDisabled is enabled, allows man-in-the-middle attackers to spoof clients via unspecified vectors.

Patch / fix

  • go stdlib 1.3.2
  • go openSUSE Tumbleweed 1.7.0-2.1
  • go1.10 openSUSE Tumbleweed 1.10.8-8.2
  • go1.11 openSUSE Tumbleweed 1.11.13-10.5
  • go1.12 openSUSE Tumbleweed 1.12.17-4.8
  • go1.4 openSUSE Tumbleweed 1.4.3-12.2
  • go1.9 openSUSE Tumbleweed 1.9.7-11.2

opensuse advisories openSUSE-SU-2024:10028-1openSUSE-SU-2024:10803-1openSUSE-SU-2024:10804-1openSUSE-SU-2024:10805-1openSUSE-SU-2024:10811-1openSUSE-SU-2024:10812-1

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-2014-7189 updated cvss 5.8

golang: TLS client authentication issue fixed in version 1.3.2

  • 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

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

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
go stdlib
>=1.1.0-0, <1.3.2
1.3.2

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.