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

> An attacker with physical access can disclose RAM contents via a custom client, requiring an upgrade to the signer application.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-frqc-62hv-379p

## What is CVE-2024-32482?

CVE-2024-32482 is a low-severity vulnerability in tillitis tkey-device-signer, published on 23 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-32482?


## How do I fix CVE-2024-32482?

No fix has been published for CVE-2024-32482 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-32482 being exploited?

There is no known exploitation of CVE-2024-32482 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32482 and fix it if it is affected.

What it is: CVE-2024-32482 is a low-severity vulnerability in tillitis tkey-device-signer, published on 23 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32482 in the wild and no public exploit code.

Affected product: tillitis tkey-device-signer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-32482/ (Markdown: https://insights.sbomify.com/CVE-2024-32482/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32482
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32482
- OSV: https://osv.dev/vulnerability/CVE-2024-32482

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32482/
Summaries are generated and may contain mistakes; the official description above is the record.