CVE-2016-10517
First published: Tue Oct 24 2017(Updated: )
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).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Redis Labs Redis | <3.2.7 |
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-2016-10517?
CVE-2016-10517 is considered a medium severity vulnerability due to the potential for Cross Protocol Scripting.
How do I fix CVE-2016-10517?
To fix CVE-2016-10517, upgrade to Redis version 3.2.7 or later.
What systems are affected by CVE-2016-10517?
CVE-2016-10517 affects all versions of Redis before 3.2.7.
What type of vulnerability is CVE-2016-10517?
CVE-2016-10517 is a Cross Protocol Scripting vulnerability that can lead to unexpected behavior in Redis.
Is CVE-2016-10517 related to HTTP requests?
Yes, CVE-2016-10517 can be triggered by HTTP requests that include invalid POST and Host: strings in the Redis protocol.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/author
- agent/description
- agent/event
- agent/softwarecombine
- agent/trending
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/redislabs
- canonical/redis