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).
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.15%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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).
- CVSS 3.0
- 7.4 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
- EPSS
- 2.15% probability · 81th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-254
- Affected
- redislabs/redis
- Source
- cve@mitre.org
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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.