# CVE-2019-10192: Memory corruption in redis

> Heap buffer overflow in Redis hyperloglog allows attackers to write beyond buffer bounds, potentially causing crashes or code execution.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-10192, CLEANSTART-2026-XD35683, DEBIAN-CVE-2019-10192, DLA-1850-1, GHSA-pgcv-crqq-f8x5, RHSA-2019:2506, RHSA-2019:2508, RHSA-2019:2621, RHSA-2019:2628, RHSA-2019:2630, UBUNTU-CVE-2019-10192, USN-4061-1

## What is CVE-2019-10192?

CVE-2019-10192 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 11 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A heap-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before 3.2.13, 4.x before 4.0.14 and 5.x before 5.0.4. By carefully corrupting a hyperloglog using the SETRANGE command, an attacker could trick Redis interpretation of dense HLL encoding to write up to 3 bytes beyond the end of a heap-allocated buffer.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

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

It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | Red Hat:openstack-optools:9::el7 | All versions | 0:3.0.6-5.el7ost |
| `redis-debuginfo` | Red Hat:openstack-optools:9::el7 | All versions | 0:3.0.6-5.el7ost |
| `redis` | Red Hat:openstack:10::el7 | All versions | 0:3.0.6-5.el7ost |
| `redis-debuginfo` | Red Hat:openstack:10::el7 | All versions | 0:3.0.6-5.el7ost |
| `redis` | Red Hat:openstack:13::el7 | All versions | 0:3.2.8-4.el7ost |
| `redis-debuginfo` | Red Hat:openstack:13::el7 | All versions | 0:3.2.8-4.el7ost |
| `redis` | Red Hat:openstack:14::el7 | All versions | 0:3.2.8-4.el7ost |
| `redis-debuginfo` | Red Hat:openstack:14::el7 | All versions | 0:3.2.8-4.el7ost |
| `redis` | Red Hat:openstack:9::el7 | All versions | 0:3.0.6-5.el7ost |
| `redis-debuginfo` | Red Hat:openstack:9::el7 | All versions | 0:3.0.6-5.el7ost |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Oracle Communications Operations Monitor, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Openstack, Redhat Software Collections, Redislabs Redis.

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

Upgrade to a fixed version.

## Is CVE-2019-10192 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10192 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 11 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10192 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-10192/ (Markdown: https://insights.sbomify.com/CVE-2019-10192/index.md)
```

## Sources

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

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