7.2
CWE
119 787 122
Advisory Published
CVE Published
Updated

CVE-2019-10192: Buffer Overflow

First published: Tue Jun 25 2019(Updated: )

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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/Redis<3.2.13
3.2.13
redhat/Redis<4.0.14
4.0.14
redhat/Redis<5.0.4
5.0.4
debian/redis
5:6.0.16-1+deb11u2
5:6.0.16-1+deb11u3
5:7.0.15-1~deb12u1
5:7.0.15-1
Redis Labs Redis>=3.0.0<3.2.13
Redis Labs Redis>=4.0.0<4.0.14
Redis Labs Redis>=5.0<5.0.4
redhat openstack=9
redhat openstack=10
redhat openstack=13
redhat openstack=14
redhat software collections=1.0
Red Hat Enterprise Linux=8.0
redhat enterprise Linux eus=8.1
redhat enterprise Linux eus=8.2
redhat enterprise Linux eus=8.4
redhat enterprise Linux server aus=8.2
redhat enterprise Linux server aus=8.4
redhat enterprise Linux server tus=8.2
redhat enterprise Linux server tus=8.4
Debian GNU/Linux=9.0
Debian GNU/Linux=10.0
Ubuntu Linux=16.04
Ubuntu Linux=18.04
Ubuntu Linux=19.04
Oracle Communications Operations Monitor=3.4
Oracle Communications Operations Monitor=4.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2019-10192?

    The severity of CVE-2019-10192 is high, with a severity value of 7.2.

  • Which versions of Redis are affected by CVE-2019-10192?

    The Redis versions 3.x before 3.2.13, 4.x before 4.0.14, and 5.x before 5.0.4 are affected by CVE-2019-10192.

  • How can an attacker exploit the vulnerability in CVE-2019-10192?

    An attacker can exploit the vulnerability in CVE-2019-10192 by carefully corrupting a hyperloglog using the SETRANGE command.

  • Is there a fix available for CVE-2019-10192?

    Yes, there are fixes available for CVE-2019-10192. Please refer to the references for more information.

  • Where can I find more information about CVE-2019-10192?

    You can find more information about CVE-2019-10192 in the provided references.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203