Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1293448 - (CVE-2015-8618) CVE-2015-8618 golang: Carry propagation in Int.Exp Montgomery code in math/big library
CVE-2015-8618 golang: Carry propagation in Int.Exp Montgomery code in math/bi...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20151221,reported=2...
: Security
Depends On: 1293449 1293451
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-21 14:05 EST by Adam Mariš
Modified: 2016-12-05 11:01 EST (History)
24 users (show)

See Also:
Fixed In Version: Go 1.5.3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-05 11:01:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2015-12-21 14:05:03 EST
Carry propagation in Int.Exp Montgomery function was found in golang's math/big library, similar to CVE-2015-3193. This issue was introduced in the 1.5 release and remains present in 1.5.1 and 1.5.2.

Upstream patch:

https://go-review.googlesource.com/#/c/17672/

CVE request:

http://seclists.org/oss-sec/2015/q4/550
Comment 1 Adam Mariš 2015-12-21 14:06:04 EST
Created golang tracking bugs for this issue:

Affects: epel-6 [bug 1293449]
Affects: fedora-all [bug 1293451]
Comment 2 Fedora Update System 2016-01-17 12:50:34 EST
golang-1.5.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Comment 3 Fedora Update System 2016-01-25 22:20:20 EST
golang-1.5.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.