Payara Server/Micro up to 6.2024.12 REST Management Interface response splitting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Payara Server and Micro up to 4.1.2.191.51/5.70.0/5.2022.5/6.21.0/6.2024.12. This issue affects some unknown processing of the component REST Management Interface Module. Such manipulation leads to response splitting. This vulnerability is documented as CVE-2024-45687. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Payara Server and Micro up to 4.1.2.191.51/5.70.0/5.2022.5/6.21.0/6.2024.12. Affected by this issue is an unknown part of the component REST Management Interface Module. 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. CVE summarizes:
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in Payara Platform Payara Server (Grizzly, REST Management Interface modules), Payara Platform Payara Micro (Grizzly modules) allows Manipulating State, Identity Spoofing.This issue affects Payara Server: from 4.1.151 through 4.1.2.191.51, from 5.20.0 through 5.70.0, from 5.2020.2 through 5.2022.5, from 6.2022.1 through 6.2024.12, from 6.0.0 through 6.21.0; Payara Micro: from 4.1.152 through 4.1.2.191.51, from 5.20.0 through 5.70.0, from 5.2020.2 through 5.2022.5, from 6.2022.1 through 6.2024.12, from 6.0.0 through 6.21.0.
The advisory is shared for download at docs.payara.fish. This vulnerability is handled as CVE-2024-45687 since 09/04/2024. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/21/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
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
- 4.1.2.191.51
- 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
- 5.68
- 5.69
- 5.70.0
- 5.2022.0
- 5.2022.1
- 5.2022.2
- 5.2022.3
- 5.2022.4
- 5.2022.5
- 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.19
- 6.20
- 6.21.0
- 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
- 6.2024.10
- 6.2024.11
- 6.2024.12
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: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: Response splittingCWE: CWE-113 / CWE-93 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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
09/04/2024 🔍01/21/2025 🔍
01/21/2025 🔍
01/21/2025 🔍
Sources
Advisory: docs.payara.fishStatus: Confirmed
CVE: CVE-2024-45687 (🔍)
GCVE (CVE): GCVE-0-2024-45687
GCVE (VulDB): GCVE-100-292736
Entry
Created: 01/21/2025 18:29Changes: 01/21/2025 18:29 (65)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.