CVE-2016-3959: 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…
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.3% (FIRST EPSS); higher than 91.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: stdlib (Go) 1.6.1, 1.5.4; go (openSUSE:Tumbleweed) 1.7.0-2.1; go1.10 (openSUSE:Tumbleweed) 1.10.8-8.2.
Low priority for now. Upgrade to stdlib (Go) 1.6.1, 1.5.4; go (openSUSE:Tumbleweed) 1.7.0-2.1; go1.10 (openSUSE:Tumbleweed) 1.10.8-8.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 23, 2016
- Updated
- Jun 16, 2026
- EPSS
- 4.3% · 91th percentile
- CWE
- CWE-20
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| golang | go | cpe:2.3:a:golang:go |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora22
- fedoraproject fedora23
- fedoraproject fedora24
- golang goup to 1.5 inclusive
- golang go1.6
- opensuse leap42.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | stdlib | from 1.6.0-0 · before 1.6.1 | 1.6.1 |
| Go | stdlib | before 1.5.4 | 1.5.4 |
| openSUSE:Tumbleweed | go | before 1.7.0-2.1 | 1.7.0-2.1 |
| openSUSE:Tumbleweed | go1.10 | before 1.10.8-8.2 | 1.10.8-8.2 |
| openSUSE:Tumbleweed | go1.11 | before 1.11.13-10.5 | 1.11.13-10.5 |
| openSUSE:Tumbleweed | go1.12 | before 1.12.17-4.8 | 1.12.17-4.8 |
| openSUSE:Tumbleweed | go1.9 | before 1.9.7-11.2 | 1.9.7-11.2 |
| Red Hat:enterprise_linux:7::server | golang | before 0:1.6.3-1.el7_2.1 | 0:1.6.3-1.el7_2.1 |
| Red Hat:enterprise_linux:7::server | golang-bin | before 0:1.6.3-1.el7_2.1 | 0:1.6.3-1.el7_2.1 |
| Red Hat:enterprise_linux:7::server | golang-docs | before 0:1.6.3-1.el7_2.1 | 0:1.6.3-1.el7_2.1 |
| Red Hat:enterprise_linux:7::server | golang-misc | before 0:1.6.3-1.el7_2.1 | 0:1.6.3-1.el7_2.1 |
| Red Hat:enterprise_linux:7::server | golang-src | before 0:1.6.3-1.el7_2.1 | 0:1.6.3-1.el7_2.1 |
| Red Hat:enterprise_linux:7::server | golang-tests | before 0:1.6.3-1.el7_2.1 | 0:1.6.3-1.el7_2.1 |
Same product
opensuse: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-0749The smartcard interaction in SPICE allows remote attackers to cause a denial of service (QEMU-KVM process crash) or possibly execute…42Plan
- CVE-2015-8863Off-by-one error in the tokenadd function in jv_parse.c in jq allows remote attackers to cause a denial of service (crash) via a long…41Plan
- CVE-2019-18903wicked: Use-after-free when receiving invalid DHCP6 IA_PD option40Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-4036Apr 18, 2016 · The quagga package before 0.99.23-2.6.1 in openSUSE and SUSE Linux Enterprise Server 11 SP 1 uses weak permissions for /etc/quagga, which…22Monitor
- ← EarlierCVE-2016-3627May 17, 2016 · The xmlStringGetNodeList function in tree.c in libxml2 2.9.3 and earlier, when used in recovery mode, allows context-dependent attackers to…32Monitor
- Later →CVE-2016-4414Jun 13, 2016 · The onReadyRead function in core/coreauthhandler.cpp in Quassel before 0.12.4 allows remote attackers to cause a denial of service (NULL…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:stdlib | 1.5.4 | Package registry (OSV) |
| Go:stdlib | 1.6.1 | Package registry (OSV) |
| opensuse:go | 1.7.0-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.10 | 1.10.8-8.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.11 | 1.11.13-10.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.12 | 1.12.17-4.8 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.9 | 1.9.7-11.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:golang | 0:1.6.3-1.el7_2.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:golang-bin | 0:1.6.3-1.el7_2.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:golang-docs | 0:1.6.3-1.el7_2.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:golang-misc | 0:1.6.3-1.el7_2.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:golang-src | 0:1.6.3-1.el7_2.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:golang-tests | 0:1.6.3-1.el7_2.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2016-04-10 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-44 d
- Published
- TodayNov 16, 2026+3828 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- lists.fedoraproject.org/pipermail/package-announce/2016-April/182526.html
- lists.fedoraproject.org/pipermail/package-announce/2016-April/183106.html
- lists.fedoraproject.org/pipermail/package-announce/2016-April/183137.html
- lists.opensuse.org/opensuse-updates/2016-05/msg00077.html
- rhn.redhat.com/errata/RHSA-2016-1538.html
- www.openwall.com/lists/oss-security/2016/04/05/1
- go-review.googlesource.com/#/c/21533/
- groups.google.com/forum/#%21topic/golang-announce/9eqIHqaWvck
Vendor advisories and official records. Exploit/PoC links are deliberately left out.