AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 60 Monero

Scope cached ShopinBit attachments by customer key

Public commit record

What the developer wrote

Authored by sneurlax

73/100 · Adequate
Scope cached ShopinBit attachments by customer key

TorAwareNetworkImage keys its cache on the url alone, so an attachment
path fetched under one customer key would be served from cache to a
later customer key without an authenticated request. Add an optional
cacheScope that is part of the key, and pass the ShopinBit customer key
there. The bearer token stays out of the key so a refreshed token does
not refetch.

The key is captured together with the request response rather than read
from the widget when building the image: FutureBuilder keeps showing the
previous snapshot while a new future is pending, and that snapshot must
not be paired with a later customer's scope.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a privacy bug in Stack Wallet's image caching. When the app showed customer support attachments from ShopinBit, it cached images using only the web address. Because the same attachment path can return different files for different customers, a later customer could briefly see another customer's cached image without a fresh permission check. The patch adds a 'customer key' to the cache key so each customer's images stay separate, and it makes sure the key is tied to the actual downloaded response rather than the on-screen widget state.

Recommended action

Treat as a privacy/security fix. Verify the patch is included in the next release, confirm no other ImageProvider in the codebase caches authenticated content by URL alone, and consider auditing other customer-keyed network resources for similar cache-key issues.

Security signals we found

01

Cross-customer cache contamination in authenticated image provider

02

Missing authorization boundary in shared URL cache key

03

FutureBuilder stale-snapshot mismatch with changing customer identity

04

Privacy leak of customer support attachments

Risk score

Why this scored 60/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 8/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.