Security readout for executives and security teams
Older Redis 3.x, 4.x, and 5.x releases have a memory corruption bug in HyperLogLog handling. A highly privileged authenticated attacker with network access could trigger serious impact, including service disruption or compromise risk. The provided sources rate it high, but do not show active exploitation. Exposure is most likely where legacy Redis 3.x, 4.x, or early 5.x instances remain deployed, especially if reachable over a network and usable by highly privileged authenticated users or applications. Prioritize remediation for internet-reachable, shared, or business-critical Redis systems. Internal isolated instances with strict privileged access are lower urgency, but still should be patched because the impact rating includes confidentiality, integrity, and availability compromise. Mitigation focus: Upgrade Redis to 3.2.13, 4.0.14, 5.0.4, or a newer supported vendor build.; Apply the relevant Debian, Ubuntu, Red Hat, Gentoo, or Oracle vendor security update.; Restrict Redis network reachability to trusted hosts and application tiers..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-121: 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 lookupCVE-2019-10193 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.2HighVector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- DSA-4480CVE reference · vendor-advisory, x_refsource_DEBIAN
- 20190712 [SECURITY] [DSA 4480-1] redis security updateCVE reference · mailing-list, x_refsource_BUGTRAQ
- USN-4061-1CVE reference · vendor-advisory, x_refsource_UBUNTU
- RHSA-2019:1819CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2019:2002CVE reference · vendor-advisory, x_refsource_REDHAT
- GLSA-201908-04CVE reference · vendor-advisory, x_refsource_GENTOO
- https://www.oracle.com/security-alerts/cpujul2020.htmlCVE reference · x_refsource_MISC
- https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTESCVE reference · x_refsource_MISC
- https://raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTESCVE reference · x_refsource_MISC
- https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTESCVE reference · x_refsource_MISC
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10193CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.