Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-3959

golang: infinite loop in several big integer routines

Overview

Published
23 May 2016
Modified
17 Jun 2026
High CVE
1 Registry packages
20 OS packages
2 Linux distributions
Yes Fix available

Description

The Verify function in crypto/dsa/dsa.go in Go before 1.5.4 and 1.6.x before 1.6.1 does not properly check parameters passed to the big integer library, which might allow remote attackers to cause a denial of service (infinite loop) via a crafted public key to a program that uses HTTPS client certificates or SSH server libraries.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-20

Affected packages · 1

Packages affected by CVE-2016-3959
EcosystemPackageVulnerableFixed in
Go stdlib <1.5.4>=1.6.0-0, <1.6.1 1.5.41.6.1

Open a package to see all its vulnerabilities.

Operating systems · 6 fixes

Red Hat 1 release · 1 package

fixed 1
golang
Red Hat fixes for CVE-2016-3959
ReleasePackageFixed inAdvisory
7 golang +5 0:1.6.3-1.el7_2.1 RHSA-2016:1538

openSUSE 1 release · 5 packages

fixed 5
go1-10 go1-11 go1-12 go go1-9
openSUSE fixes for CVE-2016-3959
ReleasePackageFixed inAdvisory
Tumbleweed go1-10 +2 1.10.8-8.2 openSUSE-SU-2024:10803-1
Tumbleweed go1-11 +2 1.11.13-10.5 openSUSE-SU-2024:10804-1
Tumbleweed go1-12 +2 1.12.17-4.8 openSUSE-SU-2024:10805-1
Tumbleweed go +1 1.7.0-2.1 openSUSE-SU-2024:10028-1
Tumbleweed go1-9 +2 1.9.7-11.2 openSUSE-SU-2024:10812-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.