Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@sap-cloud-sdk/core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.9npmAmendedPublished

    Unauthorized access to data in @sap-cloud-sdk/core

    CVE-2021-41251 · GHSA-gp2f-254m-rh32

    Affected
    • npm @sap-cloud-sdk/core < 1.52.0
    Fixed in
    1.52.0· Vendor fix available
    Issue
    Impact This affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations. In some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions. By default, destination caching is disabled. If it is enabled the maximum lifetime is 5 minutes which limits the attack vector. Patches The problem was fixed by #1769 and #1770. The security for caching has been increased. The changes are released in version 1.52.0. Workarounds Disable destination caching (it is disabled by default). References destination cache API docs For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/SAP/cloud-sdk-js

    Recommended action: Upgrade to 1.52.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. UnratednpmAmendedPublished

    Improper Authorization in @sap-cloud-sdk/core

    GHSA-r2vw-jgq9-jqx2

    Affected
    • npm @sap-cloud-sdk/core >= 1.19.0, < 1.21.2
    Fixed in
    1.21.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.21.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →