CVE-2016-10517

Name: CVE-2016-10517
Creator: NVD / NIST
Published: 2017-10-24T18:29:00.197+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.15%

Last modified Jun 17, 2026

CVE-2016-10517 is a vulnerability of currently unknown severity. networking.c in Redis before 3.2.7 allows "Cross Protocol Scripting" because it lacks a check for POST and Host: strings, which are not valid in the Redis protocol (but commonly occur when an attack triggers an HTTP request to the Redis TCP port).. EPSS estimates a 2.15% chance of exploitation in the next 30 days.

Description

networking.c in Redis before 3.2.7 allows "Cross Protocol Scripting" because it lacks a check for POST and Host: strings, which are not valid in the Redis protocol (but commonly occur when an attack triggers an HTTP request to the Redis TCP port).

Metrics

EPSS Probability

2.15%

79.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-254

Affected Software

Vendor	Product	Versions
Redislabs	Redis	< 3.2.7

References

http://www.securityfocus.com/bid/101572Third Party Advisory, VDB Entry
https://github.com/antirez/redis/commit/874804da0c014a7d704b3d285aa500098a931f50Issue Tracking, Third Party Advisory
https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTESIssue Tracking, Third Party Advisory
https://www.reddit.com/r/redis/comments/5r8wxn/redis_327_is_out_important_security_fixes_inside/Issue Tracking, Third Party Advisory
http://www.securityfocus.com/bid/101572Third Party Advisory, VDB Entry
https://github.com/antirez/redis/commit/874804da0c014a7d704b3d285aa500098a931f50Issue Tracking, Third Party Advisory
https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTESIssue Tracking, Third Party Advisory
https://www.reddit.com/r/redis/comments/5r8wxn/redis_327_is_out_important_security_fixes_inside/Issue Tracking, Third Party Advisory

Timeline

Published: Oct 24, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-10517?

How severe is CVE-2016-10517?

Severity scoring for CVE-2016-10517 is pending analysis. The EPSS model estimates a 2.15% probability of exploitation in the next 30 days.

How do I fix CVE-2016-10517?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-10517?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST