LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000125: inversoft prime-jwt version prior to version 1.3.0 or prior to commit 0d94dcef0133d699f21d217e922564adbb83a...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Inversoft prime-jwt before 1.3.0. A crafted JWT with a valid header and body could be decoded and treated as valid even without a valid signature. If an application uses this library result for authentication or authorization, attackers may bypass trust checks.

Executive priority

Prioritize remediation where prime-jwt protects login, session, API, or privileged access paths. Business urgency depends on whether the affected decoder output is used as a trust decision. Without that usage, impact may be lower.

Technical view

CVE-2018-1000125 is an input validation issue in JWTDecoder.decode. The CVE states decoding can implicitly validate a JWT even when the signature is invalid or missing. The public record names the fix as version 1.3.0 or commit 0d94dcef0133d699f21d217e922564adbb83a227.

Likely exposure

Exposure is likely limited to applications using Inversoft prime-jwt before 1.3.0, especially where JWTDecoder.decode output is trusted for identity, session, or authorization decisions. The source bundle does not provide CPEs or a broader affected-product list.

Exploitation context

The CVE describes exploitation by crafting a token with a valid header and body and requesting validation. The bundle does not cite active exploitation, and KEV status is false. No exploit maturity or public exploitation evidence is provided.

Researcher notes

The available sources are sparse: no CVSS, CWE, CPE, or vendor advisory detail beyond GitHub references. Treat the core issue as a JWT signature validation bypass risk, but validate actual exposure in application code before assigning incident-level severity.

Mitigation direction

  • Upgrade prime-jwt to version 1.3.0 or later.
  • Confirm the build includes commit 0d94dcef0133d699f21d217e922564adbb83a227 or later.
  • Review authentication flows that trust JWTDecoder.decode output.
  • Check the vendor CHANGES and issue references for project-specific guidance.

Validation and detection

  • Inventory applications and lockfiles for prime-jwt versions before 1.3.0.
  • Identify code paths calling JWTDecoder.decode for authentication or authorization.
  • Verify invalid or missing JWT signatures are rejected in tests.
  • Confirm deployed artifacts use the remediated library version.
Prepared
Confidence
medium
Sources
4

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1000125 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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