How severe is GHSA-r2vw-jgq9-jqx2?

No CVSS score has been assigned to GHSA-r2vw-jgq9-jqx2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r2vw-jgq9-jqx2?

GHSA-r2vw-jgq9-jqx2 affects the following packages: @sap-cloud-sdk/core (npm). Ecosystems affected: npm.

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

Update @sap-cloud-sdk/core to 1.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r2vw-jgq9-jqx2 is resolved across your whole dependency graph.

How do I detect GHSA-r2vw-jgq9-jqx2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sap-cloud-sdk/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-r2vw-jgq9-jqx2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-r2vw-jgq9-jqx2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r2vw-jgq9-jqx2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-r2vw-jgq9-jqx2 published, and has it been updated?

GHSA-r2vw-jgq9-jqx2 was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Improper Authorization in @sap-cloud-sdk/coreGHSA-r2vw-jgq9-jqx2

GHSA-r2vw-jgq9-jqx2 is a security vulnerability in @sap-cloud-sdk/core. A fix is available for @sap-cloud-sdk/core — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦@sap-cloud-sdk/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sap-cloud-sdk/core`	≥ 1.19.0&&< 1.21.2	1.21.2`npm install @sap-cloud-sdk/core@1.21.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sap-cloud-sdk/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sap-cloud-sdk/core to 1.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r2vw-jgq9-jqx2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-r2vw-jgq9-jqx2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works