Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@sentry/react-native

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

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

  1. UnratednpmAmendedPublished

    Potential leakage of Sentry auth tokens by React Native SDK with Expo plugin

    GHSA-68c2-4mpx-qh95

    Affected
    • npm @sentry/react-native >= 5.16.0, <= 5.19.0
    Fixed in
    5.19.1· Vendor fix available
    Issue
    Impact SDK versions between and including 5.16.0 and 5.19.0 allowed Sentry auth tokens to be set in the optional authToken configuration parameter, for debugging purposes. Doing so would result in the auth token being built into the application bundle, and therefore the auth token could be potentially exposed in case the application bundle is subsequently published. You may ignore this notification if you are not using authToken configuration parameter in your React Native SDK configuration or did not publish apps using this way of configuring the authToken. If you had set the authToken in the plugin config previously, and built and published an app with that config, you should rotate your token. Patches The behavior that allowed setting an authToken parameter was fixed in SDK version 5.19.1 where, if this parameter was set, you will see a warning and the authToken would be removed before bundling the application. Workarounds 1. Remove authToken from the plugin configuration. 2. If…

    Recommended action: Upgrade to 5.19.1 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 →