# CVE-2019-17195: Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT

> Attackers can cause application crashes or bypass authentication by sending malformed JWTs to applications using the Nimbus JOSE+JWT library.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** Yes
- **Published:** 15 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** CLEANSTART-2026-EQ87084, GHSA-f6vf-pq8c-69m4, OESA-2021-1269

## What is CVE-2019-17195?

CVE-2019-17195 is a critical denial of service vulnerability in Oracle Enterprise Manager Base Platform, published on 15 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2019-17195?

2 open source packages ship an affected version, including com.nimbusds:nimbus-jose-jwt. It affects 15 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.nimbusds:nimbus-jose-jwt` | Maven | All versions | 7.9 |
| `com.nimbusds:nimbus-jose-jwt` | Maven | All versions | 7.9 |

Products: Apache Hadoop, Connect2id Nimbus Jose\+jwt, Oracle Communications Cloud Native Core Security Edge Protection Proxy, Oracle Communications Pricing Design Center, Oracle Data Integrator, Oracle Enterprise Manager Base Platform, Oracle Healthcare Data Repository, Oracle Insurance Policy Administration, Oracle Jd Edwards Enterpriseone Orchestrator, Oracle Jd Edwards Enterpriseone Tools, Oracle Peoplesoft Enterprise Peopletools, Oracle Policy Automation, Oracle Primavera Gateway, Oracle Solaris Cluster, Oracle Weblogic Server.

## How do I fix CVE-2019-17195?

Upgrade com.nimbusds:nimbus-jose-jwt to 7.9 or later.

## Is CVE-2019-17195 being exploited?

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

Public exploit code:

- CVE-2021-1994、CVE-2021-2047、CVE-2021-2064、CVE-2021-2108、CVE-2021-2075、CVE-2019-17195、CVE-2020-14756、CVE-2021-2109 (github_poc): https://github.com/somatrasss/weblogic2021

## Other vulnerabilities in Oracle Enterprise Manager Base Platform

- [CVE-2022-25168](https://insights.sbomify.com/CVE-2022-25168/): Command injection in org.apache.hadoop.fs.FileUtil.unTarUsingTar (critical 9.8)
- [CVE-2021-37404](https://insights.sbomify.com/CVE-2021-37404/): Heap buffer overflow in libhdfs native library (critical 9.8)
- [CVE-2022-26612](https://insights.sbomify.com/CVE-2022-26612/): Arbitrary file write in FileUtil#unpackEntries on Windows (critical 9.8)
- [CVE-2017-15718](https://insights.sbomify.com/CVE-2017-15718/): Exposure of Sensitive Information in Hadoop (critical 9.8)
- [CVE-2012-4449](https://insights.sbomify.com/CVE-2012-4449/): Use of a Broken or Risky Cryptographic Algorithm in Apache Hadoop (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17195 and fix it if it is affected.

What it is: CVE-2019-17195 is a critical denial of service vulnerability in Oracle Enterprise Manager Base Platform, published on 15 Oct 2019. 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-2019-17195 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.nimbusds:nimbus-jose-jwt (Maven): affected all versions; fixed in 7.9
- com.nimbusds:nimbus-jose-jwt (Maven): affected all versions; fixed in 7.9

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

## Sources

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

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