LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15005: Cryptographically weak random number generation in github.com/dinever/golf

CSRF tokens are generated using math/rand, which is not a cryptographically secure random number generator, allowing an attacker to predict values and bypass CSRF protections with relatively few requests.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the Go web framework package github.com/dinever/golf. It generated CSRF tokens with a predictable random-number source. If an application uses the vulnerable CSRF feature, an attacker may be able to guess tokens and bypass a protection meant to stop forged authenticated actions.

Executive priority

Treat as high priority where the package protects authenticated workflows such as account, payment, or admin actions. If the dependency is unused or CSRF is implemented separately, urgency is lower but version verification is still needed.

Technical view

CSRF token generation used Go math/rand instead of a cryptographically secure generator. Predictable token values can undermine CSRF validation. The supplied CVSS 3.1 score is 8.8, with network attack vector, low complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in Go applications that depend on github.com/dinever/golf and use its CSRF protection. The source bundle lists affected version data as “0,” so teams should verify exact module revisions against the Go vulnerability record and upstream commit history.

Exploitation context

The bundle does not show CISA KEV listing or cite active exploitation. The attack depends on predictability of CSRF tokens and victim interaction. Successful abuse could allow forged authenticated requests in applications relying on the vulnerable CSRF implementation.

Researcher notes

The main uncertainty is version mapping: the provided affected version field is not enough to identify all vulnerable releases. Use the CVE record, Go advisory GO-2020-0045, issue 20, pull request 24, and commit 3776f338be48b5bc5e8cf9faff7851fc52a3f1fe for confirmation.

Mitigation direction

  • Check the Go vulnerability record and upstream repository for the fixed revision.
  • Update github.com/dinever/golf to a revision containing the upstream CSRF token fix.
  • If no maintained release is available, assess replacing or vendoring the dependency.
  • Review application CSRF handling for separate cryptographic token generation safeguards.

Validation and detection

  • Inventory Go modules for github.com/dinever/golf usage.
  • Confirm whether the application uses golf’s CSRF token functionality.
  • Map deployed module revisions to the upstream fix commit and Go advisory.
  • Test CSRF protections through authorized application security testing only.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-15005 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2016-15005Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
github.com/dinever/golfgithub.com/dinever/golfgithub.com/dinever/golf, 0unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.