Skip to content
Fencer Intel
high 7.5

CVE-2015-8618 json

Incorrect calculation affecting RSA computations in math/big

published 2016-01-27 10 y ago modified 2026-06-17 4 mo ago also GO-2021-0160 , EUVD-2015-8495

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

Summary

The Int.Exp Montgomery code in the math/big library in Go 1.5.x before 1.5.3 mishandles carry propagation and produces incorrect output, which makes it easier for attackers to obtain private RSA keys via unspecified vectors.

Patch / fix

  • go stdlib 1.5.3
  • 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.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: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-2015-8618 updated cvss 2.6

golang: Carry propagation in Int.Exp Montgomery code in math/big library

  • Red Hat Enterprise Linux 7 golang, golang-bin, golang-src, golang-misc, golang-tests Red Hat OpenShift Enterprise 3 golang Red Hat Storage 3 golang, golang-bin, golang-src, golang-misc, golang-tests
    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

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

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:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
go stdlib
>=1.5.0-0, <1.5.3
1.5.3

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.