Payara Server up to 4.1.2.191.50/5.67.x/6.18.x/6.2024.9 cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Payara Server up to 4.1.2.191.50/5.67.x/6.18.x/6.2024.9. It has been rated as problematic. This impacts an unknown function. The manipulation leads to cross site scripting. This vulnerability is traded as CVE-2024-8215. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Payara Server up to 4.1.2.191.50/5.67.x/6.18.x/6.2024.9. It has been rated as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Payara Platform Payara Server (Admin Console modules) allows Remote Code Inclusion.This issue affects Payara Server: from 5.20.0 before 5.68.0, from 6.0.0 before 6.19.0, from 6.2022.1 before 6.2024.10, from 4.1.2.191.1 before 4.1.2.191.51.
The advisory is shared at docs.payara.fish. The identification of this vulnerability is CVE-2024-8215 since 08/27/2024. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. 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 4.1.2.191.51, 5.68.0, 6.19.0 or 6.2024.10 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 4.1.2.191.0
- 4.1.2.191.1
- 4.1.2.191.2
- 4.1.2.191.3
- 4.1.2.191.4
- 4.1.2.191.5
- 4.1.2.191.6
- 4.1.2.191.7
- 4.1.2.191.8
- 4.1.2.191.9
- 4.1.2.191.10
- 4.1.2.191.11
- 4.1.2.191.12
- 4.1.2.191.13
- 4.1.2.191.14
- 4.1.2.191.15
- 4.1.2.191.16
- 4.1.2.191.17
- 4.1.2.191.18
- 4.1.2.191.19
- 4.1.2.191.20
- 4.1.2.191.21
- 4.1.2.191.22
- 4.1.2.191.23
- 4.1.2.191.24
- 4.1.2.191.25
- 4.1.2.191.26
- 4.1.2.191.27
- 4.1.2.191.28
- 4.1.2.191.29
- 4.1.2.191.30
- 4.1.2.191.31
- 4.1.2.191.32
- 4.1.2.191.33
- 4.1.2.191.34
- 4.1.2.191.35
- 4.1.2.191.36
- 4.1.2.191.37
- 4.1.2.191.38
- 4.1.2.191.39
- 4.1.2.191.40
- 4.1.2.191.41
- 4.1.2.191.42
- 4.1.2.191.43
- 4.1.2.191.44
- 4.1.2.191.45
- 4.1.2.191.46
- 4.1.2.191.47
- 4.1.2.191.48
- 4.1.2.191.49
- 4.1.2.191.50
- 5.0
- 5.1
- 5.2
- 5.3
- 5.4
- 5.5
- 5.6
- 5.7
- 5.8
- 5.9
- 5.10
- 5.11
- 5.12
- 5.13
- 5.14
- 5.15
- 5.16
- 5.17
- 5.18
- 5.19
- 5.20
- 5.21
- 5.22
- 5.23
- 5.24
- 5.25
- 5.26
- 5.27
- 5.28
- 5.29
- 5.30
- 5.31
- 5.32
- 5.33
- 5.34
- 5.35
- 5.36
- 5.37
- 5.38
- 5.39
- 5.40
- 5.41
- 5.42
- 5.43
- 5.44
- 5.45
- 5.46
- 5.47
- 5.48
- 5.49
- 5.50
- 5.51
- 5.52
- 5.53
- 5.54
- 5.55
- 5.56
- 5.57
- 5.58
- 5.59
- 5.60
- 5.61
- 5.62
- 5.63
- 5.64
- 5.65
- 5.66
- 5.67
- 6.0
- 6.1
- 6.2
- 6.3
- 6.4
- 6.5
- 6.6
- 6.7
- 6.8
- 6.9
- 6.10
- 6.11
- 6.12
- 6.13
- 6.14
- 6.15
- 6.16
- 6.17
- 6.18
- 6.2024.0
- 6.2024.1
- 6.2024.2
- 6.2024.3
- 6.2024.4
- 6.2024.5
- 6.2024.6
- 6.2024.7
- 6.2024.8
- 6.2024.9
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.3
VulDB Base Score: 2.4
VulDB Temp Score: 2.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: 🔍
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Payara Server 4.1.2.191.51/5.68.0/6.19.0/6.2024.10
Timeline
08/27/2024 🔍10/08/2024 🔍
10/08/2024 🔍
10/08/2024 🔍
Sources
Advisory: docs.payara.fishStatus: Confirmed
CVE: CVE-2024-8215 (🔍)
GCVE (CVE): GCVE-0-2024-8215
GCVE (VulDB): GCVE-100-279629
Entry
Created: 10/08/2024 18:55Changes: 10/08/2024 18:55 (65)
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.