# GHSA-r2vw-jgq9-jqx2: Improper Authorization in @sap-cloud-sdk/core

> Attackers can bypass authentication by providing a manipulated JWT with a trusted URL for the verification key.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-r2vw-jgq9-jqx2?

GHSA-r2vw-jgq9-jqx2 is an authentication bypass vulnerability in @sap-cloud-sdk/core, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of `@sap-cloud-sdk/core` do not properly validate JWTs.  The `verifyJwt()` function does not properly validate the URL from where the public verification key for the JWT can be downloaded.  Any URL was trusted which makes it possible to provide a URL belonging to a manipulated JWT.

## Recommendation

Upgrade to version 1.21.2 or later.

## Which versions are affected by GHSA-r2vw-jgq9-jqx2?

2 open source packages ship an affected version, including @sap-cloud-sdk/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@sap-cloud-sdk/core` | npm | From 1.19.0 | 1.21.2 |
| `@sap-cloud-sdk/core` | npm | From 1.19.0 | 1.21.2 |

## How do I fix GHSA-r2vw-jgq9-jqx2?

Upgrade @sap-cloud-sdk/core to 1.21.2 or later.

## Is GHSA-r2vw-jgq9-jqx2 being exploited?

There is no known exploitation of GHSA-r2vw-jgq9-jqx2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-r2vw-jgq9-jqx2 and fix it if it is affected.

What it is: GHSA-r2vw-jgq9-jqx2 is an authentication bypass vulnerability in @sap-cloud-sdk/core, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-r2vw-jgq9-jqx2 in the wild and no public exploit code.

Affected packages and fixed versions:
- @sap-cloud-sdk/core (npm): affected from 1.19.0; fixed in 1.21.2
- @sap-cloud-sdk/core (npm): affected from 1.19.0; fixed in 1.21.2

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/GHSA-r2vw-jgq9-jqx2/ (Markdown: https://insights.sbomify.com/GHSA-r2vw-jgq9-jqx2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-r2vw-jgq9-jqx2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-r2vw-jgq9-jqx2/
Summaries are generated and may contain mistakes; the official description above is the record.