IBM WebSphere Commerce up to 6.0.0.11/7.0.0.8 HTTP Header response splitting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $25k-$100k | 0.00 |
Summary
A vulnerability classified as problematic has been found in IBM WebSphere Commerce up to 6.0.0.11/7.0.0.8. Affected by this vulnerability is an unknown functionality of the component HTTP Header Handler. Performing a manipulation results in response splitting. This vulnerability is identified as CVE-2015-0196. There is not any exploit available.
Details
A vulnerability classified as critical has been found in IBM WebSphere Commerce up to 6.0.0.11/7.0.0.8 (Application Server Software). This affects some unknown processing of the component HTTP Header Handler. The manipulation with an unknown input leads to a response splitting vulnerability. CWE is classifying the issue as CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
CRLF injection vulnerability in IBM WebSphere Commerce 6.0 through 6.0.0.11 and 7.0 before 7.0.0.8 Cumulative iFix 2 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URL.
The weakness was released 06/29/2015 (Website). It is possible to read the advisory at www-01.ibm.com. This vulnerability is uniquely identified as CVE-2015-0196 since 11/18/2014. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 04/20/2019).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 6.0.0.0
- 6.0.0.1
- 6.0.0.2
- 6.0.0.3
- 6.0.0.4
- 6.0.0.5
- 6.0.0.6
- 6.0.0.7
- 6.0.0.8
- 6.0.0.9
- 6.0.0.10
- 6.0.0.11
- 7.0.0.0
- 7.0.0.1
- 7.0.0.2
- 7.0.0.3
- 7.0.0.4
- 7.0.0.5
- 7.0.0.6
- 7.0.0.7
- 7.0.0.8
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Response splittingCWE: CWE-113 / CWE-93 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/18/2014 🔍06/29/2015 🔍
06/29/2015 🔍
06/30/2015 🔍
04/20/2019 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-0196 (🔍)
GCVE (CVE): GCVE-0-2015-0196
GCVE (VulDB): GCVE-100-76131
Entry
Created: 06/30/2015 10:09Updated: 04/20/2019 01:23
Changes: 06/30/2015 10:09 (48), 04/20/2019 01:23 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.