IBM WebSphere eXtreme Scale up to 7.1.0.2/7.1.1.0 response splitting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in IBM WebSphere eXtreme Scale up to 7.1.0.2/7.1.1.0 and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation leads to response splitting. This vulnerability is documented as CVE-2015-2028. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, has been found in IBM WebSphere eXtreme Scale up to 7.1.0.2/7.1.1.0 (Application Server Software). This issue affects an unknown part. The manipulation with an unknown input leads to a response splitting vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
CRLF injection vulnerability in IBM WebSphere eXtreme Scale 7.1.0 before 7.1.0.3 and 7.1.1 before 7.1.1.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URL.
The weakness was released 10/04/2015 (Website). The advisory is shared at www-01.ibm.com. The identification of this vulnerability is CVE-2015-2028 since 02/19/2015. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 7.1.0.3 or 7.1.1.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 76716†) and Vulnerability Center (SBV-54229†). Entries connected to this vulnerability are available at VDB-78218, VDB-78219, VDB-78220 and VDB-78222. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
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.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: UpgradeStatus: 🔍
Upgrade: WebSphere eXtreme Scale 7.1.0.3/7.1.1.1
Timeline
02/19/2015 🔍09/04/2015 🔍
09/04/2015 🔍
10/03/2015 🔍
10/04/2015 🔍
10/06/2015 🔍
11/05/2015 🔍
03/11/2018 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-2028 (🔍)
GCVE (CVE): GCVE-0-2015-2028
GCVE (VulDB): GCVE-100-78221
SecurityFocus: 76716 - IBM WebSphere eXtreme Scale CVE-2015-2028 HTTP Response Splitting Vulnerability
Vulnerability Center: 54229 - IBM WebSphere eXtreme Scale Remote CRLF via a Crafted URL - CVE-2015-2028, Medium
See also: 🔍
Entry
Created: 10/06/2015 11:32Updated: 03/11/2018 08:56
Changes: 10/06/2015 11:32 (54), 03/11/2018 08:56 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.