i-filter up to 9.50R05 HTTP Response Splitting response splitting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in i-filter up to 9.50R05. Impacted is an unknown function. The manipulation results in response splitting (HTTP Response Splitting). This vulnerability is reported as CVE-2018-16181. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, was found in i-filter up to 9.50R05. Affected is an unknown functionality. The manipulation with an unknown input leads to a response splitting vulnerability (HTTP Response Splitting). 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. CVE summarizes:
HTTP header injection vulnerability in i-FILTER Ver.9.50R05 and earlier may allow remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks that may result in an arbitrary script injection or setting an arbitrary cookie values via unspecified vectors.
The bug was discovered 12/07/2018. The weakness was disclosed 01/09/2019 (Website). The advisory is shared for download at jvn.jp. This vulnerability is traded as CVE-2018-16181 since 08/30/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 33 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-128891 is pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
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
Name: HTTP Response SplittingClass: Response splitting / HTTP Response Splitting
CWE: 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
08/30/2018 🔍12/07/2018 🔍
01/09/2019 🔍
01/09/2019 🔍
01/10/2019 🔍
04/27/2020 🔍
Sources
Advisory: jvn.jpStatus: Not defined
CVE: CVE-2018-16181 (🔍)
GCVE (CVE): GCVE-0-2018-16181
GCVE (VulDB): GCVE-100-128892
See also: 🔍
Entry
Created: 01/10/2019 13:57Updated: 04/27/2020 16:42
Changes: 01/10/2019 13:57 (56), 04/27/2020 16:42 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.