Apache Allura up to 1.8.0 HTTP Response Splitting cross site scripting

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Apache Allura up to 1.8.0. This affects an unknown function. This manipulation causes cross site scripting (HTTP Response Splitting). This vulnerability is handled as CVE-2018-1319. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical was found in Apache Allura up to 1.8.0. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a cross site scripting vulnerability (HTTP Response Splitting). The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Apache Allura prior to 1.8.1, attackers may craft URLs that cause HTTP response splitting. If a victim goes to a maliciously crafted URL, unwanted results may occur including XSS or service denial for the victim's browsing session.
The bug was discovered 03/15/2018. The weakness was released 03/15/2018 (Website). The advisory is shared at lists.apache.org. This vulnerability is known as CVE-2018-1319 since 12/07/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 1.8.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103434†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: Cross site scripting / HTTP Response Splitting
CWE: CWE-79 / CWE-94 / 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: 🔍
0-Day Time: 🔍
Upgrade: Allura 1.8.1
Timeline
12/07/2017 🔍03/15/2018 🔍
03/15/2018 🔍
03/15/2018 🔍
03/15/2018 🔍
03/16/2018 🔍
02/05/2021 🔍
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Researcher: Everardo Padilla Saca
Status: Not defined
CVE: CVE-2018-1319 (🔍)
GCVE (CVE): GCVE-0-2018-1319
GCVE (VulDB): GCVE-100-114661
SecurityFocus: 103434 - APACHE Allura CVE-2018-1319 HTTP Response Splitting Vulnerability
Entry
Created: 03/16/2018 08:15Updated: 02/05/2021 10:55
Changes: 03/16/2018 08:15 (60), 01/14/2020 09:22 (3), 02/05/2021 10:55 (3)
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.