CVE-2015-5206
First published: Wed Sep 13 2017(Updated: )
Unspecified vulnerability in the HTTP/2 experimental feature in Apache Traffic Server before 5.3.x before 5.3.2 has unknown impact and attack vectors, a different vulnerability than CVE-2015-5168.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache Traffic Server | =5.3.0 | |
| Apache Traffic Server | =5.3.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-2015-5206?
The severity level of CVE-2015-5206 is currently unknown due to unspecified impact and attack vectors.
How do I fix CVE-2015-5206?
To fix CVE-2015-5206, upgrade Apache Traffic Server to version 5.3.2 or later.
Which versions of Apache Traffic Server are affected by CVE-2015-5206?
CVE-2015-5206 affects Apache Traffic Server versions 5.3.0 and 5.3.1.
Can CVE-2015-5206 be exploited remotely?
The attack vectors for CVE-2015-5206 are not clearly defined, leaving the potential for remote exploitation unknown.
Is CVE-2015-5206 related to any other vulnerabilities?
CVE-2015-5206 is a different vulnerability than CVE-2015-5168, though both are associated with the HTTP/2 feature in Apache Traffic Server.
- collector/nvd-index
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- agent/references
- agent/description
- agent/softwarecombine
- agent/type
- agent/first-publish-date
- agent/event
- agent/tags
- agent/source
- vendor/apache
- canonical/apache traffic server
- version/apache traffic server/5.3.0
- version/apache traffic server/5.3.1