# CVE-2019-13052: Weak cryptography in n/a

> Attackers can decrypt keystrokes from Logitech Unifying devices by sniffing the pairing process, compromising user privacy.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v2rp-7mmr-qgr5

## What is CVE-2019-13052?

CVE-2019-13052 is a medium-severity vulnerability in n/a, published on 29 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Logitech Unifying devices allow live decryption if the pairing of a keyboard to a receiver is sniffed.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2019-13052?

It affects 1 product.


Products: Logitech Unifying Receiver Firmware.

## How do I fix CVE-2019-13052?

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

## Is CVE-2019-13052 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13053](https://insights.sbomify.com/CVE-2019-13053/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13052 and fix it if it is affected.

What it is: CVE-2019-13052 is a medium-severity vulnerability in n/a, published on 29 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13052 in the wild and no public exploit code.

Affected product: n/a. 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-2019-13052/ (Markdown: https://insights.sbomify.com/CVE-2019-13052/index.md)
```

## Sources

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

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