# CVE-2015-10004: Timing side-channel in github.com/robbert229/jwt

> An attacker can determine the expected HMAC via timing side-channels in token validation, potentially compromising authentication integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2022
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-5vw4-v588-pgv8, GO-2020-0023

## What is CVE-2015-10004?

CVE-2015-10004 is a high-severity vulnerability in github.com/robbert229/jwt, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Token validation methods are susceptible to a timing side-channel during HMAC comparison. With a large enough number of requests over a low latency connection, an attacker may use this to determine the expected HMAC.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2015-10004?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/robbert229/jwt` | Go | All versions | 0.0.0-20170426191122-ca1404ee6e83 |
| `github.com/robbert229/jwt` | Go | All versions | 0.0.0-20170426191122-ca1404ee6e83 |
| `github.com/robbert229/jwt` | Go | All versions | 0.0.0-20170426191122-ca1404ee6e83 |

Products: Json Web Token Project Json Web Token.

## How do I fix CVE-2015-10004?

Upgrade github.com/robbert229/jwt to 0.0.0-20170426191122-ca1404ee6e83 or later.

## Is CVE-2015-10004 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10004 and fix it if it is affected.

What it is: CVE-2015-10004 is a high-severity vulnerability in github.com/robbert229/jwt, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-10004 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/robbert229/jwt (Go): affected all versions; fixed in 0.0.0-20170426191122-ca1404ee6e83
- github.com/robbert229/jwt (Go): affected all versions; fixed in 0.0.0-20170426191122-ca1404ee6e83
- github.com/robbert229/jwt (Go): affected all versions; fixed in 0.0.0-20170426191122-ca1404ee6e83

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-2015-10004/ (Markdown: https://insights.sbomify.com/CVE-2015-10004/index.md)
```

## Sources

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

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