When the Mira Android app opens in-app WebView content (e.g., shop redirect flows), the user's live session token is appended to the URL as a query string parameter, and a persistent user identifier is included in the WebView's User-Agent header. Both are then transmitted to third-party web properties, referrer logs, and any JavaScript running in the WebView context.
Summary
AIThe Mira Android app puts a live session token in the URL and a persistent user identifier in the User-Agent header when it opens in-app WebView content. When a user opens that content, the values can reach third-party web properties, referrer logs, and JavaScript running in the WebView.
Who should check
Teams running the Mira Android app should check their deployments; affected versions were not specified.
What to do
- 1Consult the vendor advisory for affected versions and remediation.