Advisory

GHSA-68c2-4mpx-qh95

Also known as: None

Summary

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

Details

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 you had set the authToken in the plugin config previously, and built and published an app with that config, you should rotate your token.

References

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-03-01 16:57 UTC
Modified
2024-03-01 16:57 UTC

Affected packages and fixes

@sentry/react-native

npm · All systems

Affected

  • introduced 5.16.0, fixed 5.19.1 (semver)

Fixed versions

5.19.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences