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

> Attackers can predict CSRF tokens due to weak random number generation, bypassing CSRF protections in the Golf web framework.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Dec 2022
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-q9qr-jwpw-3qvv, GO-2020-0045

## What is CVE-2016-15005?

CVE-2016-15005 is a high-severity vulnerability in github.com/dinever/golf, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2016-15005?

3 open source packages ship an affected version, including github.com/dinever/golf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dinever/golf` | Go | All versions | 0.3.0 |
| `github.com/dinever/golf` | Go | All versions | 0.3.0 |
| `github.com/dinever/golf` | Go | All versions | 0.3.0 |

Products: Golf Project Golf.

## How do I fix CVE-2016-15005?

Upgrade github.com/dinever/golf to 0.3.0 or later.

## Is CVE-2016-15005 being exploited?

There is no known exploitation of CVE-2016-15005 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15005 and fix it if it is affected.

What it is: CVE-2016-15005 is a high-severity vulnerability in github.com/dinever/golf, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-15005 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/dinever/golf (Go): affected all versions; fixed in 0.3.0
- github.com/dinever/golf (Go): affected all versions; fixed in 0.3.0
- github.com/dinever/golf (Go): affected all versions; fixed in 0.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-15005/ (Markdown: https://insights.sbomify.com/CVE-2016-15005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-15005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-15005
- OSV: https://osv.dev/vulnerability/CVE-2016-15005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-15005/
Summaries are generated and may contain mistakes; the official description above is the record.