# CVE-2018-1000125: Security feature bypass in n/a

> Attackers can bypass JWT signature validation in prime-jwt, allowing them to forge tokens and gain unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rhv5-f6gj-fqm2

## What is CVE-2018-1000125?

CVE-2018-1000125 is a critical vulnerability in n/a, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

inversoft prime-jwt version prior to version 1.3.0 or prior to commit 0d94dcef0133d699f21d217e922564adbb83a227 contains an input validation vulnerability in JWTDecoder.decode that can result in a JWT that is decoded and thus implicitly validated even if it lacks a valid signature. This attack appear to be exploitable via an attacker crafting a token with a valid header and body and then requests it to be validated. This vulnerability appears to have been fixed in 1.3.0 and later or after commit 0d94dcef0133d699f21d217e922564adbb83a227.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-1000125?

It affects 1 product.


Products: Inversoft Prime-Jwt.

## How do I fix CVE-2018-1000125?

No fix has been published for CVE-2018-1000125 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1000125 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1000531](https://insights.sbomify.com/CVE-2018-1000531/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000125 and fix it if it is affected.

What it is: CVE-2018-1000125 is a critical vulnerability in n/a, published on 13 Mar 2018. 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-2018-1000125 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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