LiveActive security incident?Get immediate response
CVE Record

CVE-2019-10192: A heap-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before...

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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Redis instances on affected 3.x, 4.x, and 5.x releases can be crashed or potentially compromised by a highly privileged attacker who can manipulate HyperLogLog data. This is serious for exposed or shared Redis deployments, but the provided sources do not show known active exploitation.

Executive priority

Patch during the next urgent maintenance window for internet-exposed, multi-tenant, or business-critical Redis. Internal single-tenant instances still need remediation, but urgency depends on who can write to Redis and whether vendor fixes are already backported.

Technical view

CVE-2019-10192 is a CWE-122 heap-buffer overflow in Redis HyperLogLog dense encoding. A corrupted HyperLogLog value can cause Redis to write up to 3 bytes past a heap buffer. Affected versions are 3.x before 3.2.13, 4.x before 4.0.14, and 5.x before 5.0.4. CVSS v3.0 is 7.2.

Likely exposure

Exposure is limited to Redis deployments running the listed vulnerable versions or unfixed vendor builds. CVSS indicates network attackability but requires high privileges, so prioritize Redis services reachable by administrators, applications, or tenants with write capability.

Exploitation context

The source bundle describes the vulnerability mechanics but provides no KEV listing and no cited evidence of active exploitation. Treat this as a high-impact memory corruption issue requiring privileged Redis access, not as confirmed in-the-wild exploitation.

Researcher notes

Focus validation on version provenance and package backports. The CVSS privilege requirement is high, but confidentiality, integrity, and availability impacts are all rated high. Do not assume exploitability beyond the documented out-of-bounds write without additional vendor or exploitability evidence.

Mitigation direction

  • Upgrade Redis to 3.2.13, 4.0.14, 5.0.4, or later.
  • Apply fixed Redis packages from your OS vendor security advisory.
  • Confirm vendor backports if package versions do not match upstream fixed versions.
  • Retire unsupported Redis branches where no maintained fix is available.

Validation and detection

  • Inventory all Redis servers and managed Redis images.
  • Compare Redis versions against the vulnerable version ranges.
  • Verify OS package changelogs or advisories include the CVE fix.
  • Prioritize instances reachable over the network by privileged writers.
  • Run service regression tests after Redis package updates.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-10192 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
17Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.2High
CVSS 3.0 vector shape for CVE-2019-10192Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Redis Labsredis3.x before 3.2.13, 4.x before 4.0.14, 5.x before 5.0.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.