CVE-2016-10517
UnknownEPSS 2.15%
Last modified
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
Weakness Enumeration
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
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-10517?
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).
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.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-10511The Twitter iOS client versions 6.62 and 6.62.1 fail to vali…
- CVE-2016-10512MultiTech FaxFinder before 4.1.2 stores Passwords unencrypte…
- CVE-2016-10513Cross Site Scripting (XSS) exists in Piwigo before 2.8.3 via…
- CVE-2016-10514url_check_format in include/functions.inc.php in Piwigo befo…
- CVE-2016-10515In Redmine before 3.2.3, there are stored XSS vulnerabilitie…
- CVE-2016-10516Cross-site scripting (XSS) vulnerability in the render_full …
- CVE-2016-10518A vulnerability was found in the ping functionality of the w…
- CVE-2016-10519A security issue was found in bittorrent-dht before 5.1.3 th…
- CVE-2016-1052Use-after-free vulnerability in Adobe Reader and Acrobat bef…
- CVE-2016-10520jadedown is vulnerable to regular expression denial of servi…7.5
- CVE-2016-10521jshamcrest is vulnerable to regular expression denial of ser…7.5
- CVE-2016-10522rails_admin ruby gem <v1.1.1 is vulnerable to cross-site req…
Are you affected by CVE-2016-10517?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST