Eclipse Jetty up to 9.2.26/9.3.25/9.4.15 URL cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Eclipse Jetty up to 9.2.26/9.3.25/9.4.15. It has been rated as problematic. This vulnerability affects unknown code of the component URL Handler. Performing a manipulation results in cross site scripting. This vulnerability is reported as CVE-2019-10241. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Eclipse Jetty up to 9.2.26/9.3.25/9.4.15. It has been classified as problematic. This affects an unknown function of the component URL Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:
In Eclipse Jetty version 9.2.26 and older, 9.3.25 and older, and 9.4.15 and older, the server is vulnerable to XSS conditions if a remote client USES a specially formatted URL against the DefaultServlet or ResourceHandler that is configured for showing a Listing of directory contents.
The bug was discovered 04/22/2019. The weakness was disclosed 04/22/2019 (Website). The advisory is shared at bugs.eclipse.org. This vulnerability is uniquely identified as CVE-2019-10241 since 03/27/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 13485 (Eclipse Jetty XSS Vulnerability(Bug 546121)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-133919 and VDB-133918 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 9.2.0
- 9.2.1
- 9.2.2
- 9.2.3
- 9.2.4
- 9.2.5
- 9.2.6
- 9.2.7
- 9.2.8
- 9.2.9
- 9.2.10
- 9.2.11
- 9.2.12
- 9.2.13
- 9.2.14
- 9.2.15
- 9.2.16
- 9.2.17
- 9.2.18
- 9.2.19
- 9.2.20
- 9.2.21
- 9.2.22
- 9.2.23
- 9.2.24
- 9.2.25
- 9.2.26
- 9.3.0
- 9.3.1
- 9.3.2
- 9.3.3
- 9.3.4
- 9.3.5
- 9.3.6
- 9.3.7
- 9.3.8
- 9.3.9
- 9.3.10
- 9.3.11
- 9.3.12
- 9.3.13
- 9.3.14
- 9.3.15
- 9.3.16
- 9.3.17
- 9.3.18
- 9.3.19
- 9.3.20
- 9.3.21
- 9.3.22
- 9.3.23
- 9.3.24
- 9.3.25
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
- 9.4.4
- 9.4.5
- 9.4.6
- 9.4.7
- 9.4.8
- 9.4.9
- 9.4.10
- 9.4.11
- 9.4.12
- 9.4.13
- 9.4.14
- 9.4.15
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.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
Class: Cross site scriptingCWE: 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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/27/2019 🔍04/22/2019 🔍
04/22/2019 🔍
04/23/2019 🔍
09/06/2023 🔍
Sources
Advisory: DLA 2661-1Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-10241 (🔍)
GCVE (CVE): GCVE-0-2019-10241
GCVE (VulDB): GCVE-100-133917
See also: 🔍
Entry
Created: 04/23/2019 08:36Updated: 09/06/2023 09:53
Changes: 04/23/2019 08:36 (57), 06/01/2020 09:21 (2), 09/06/2023 09:53 (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.