CVE-2024-45687: HTTP Server incorrectly accepting disallowed characters within header values
First published: Tue Jan 21 2025(Updated: )
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.
Credit: 769c9ae7-73c3-4e47-ae19-903170fc3eb8
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Payara Payara Server | >=4.1.151<4.1.2.191.51>=5.20.0<5.70.0>=5.2020.2<5.2022.5>=6.2022.1<6.2024.12>=6.0.0<6.21.0 | |
| Payara Micro | >=4.1.152<4.1.2.191.51>=5.20.0<5.70.0>=5.2020.2<5.2022.5>=6.2022.1<6.2024.12>=6.0.0<6.21.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-45687?
CVE-2024-45687 is classified as a moderate severity vulnerability due to its potential for manipulating state and identity spoofing.
How do I fix CVE-2024-45687?
To fix CVE-2024-45687, you should update your Payara Server or Payara Micro to the latest version that addresses this vulnerability.
Which versions are affected by CVE-2024-45687?
CVE-2024-45687 affects Payara Server versions between 4.1.151 and 4.1.2.191.51, 5.20.0 and 5.70.0, 6.0.0 and 6.21.0 as well as Payara Micro with similar version ranges.
What types of attacks can CVE-2024-45687 facilitate?
CVE-2024-45687 can facilitate HTTP request/response splitting attacks which may lead to state manipulation and identity spoofing.
Is there a workaround for CVE-2024-45687?
Currently, the best practice is to apply the necessary update to mitigate CVE-2024-45687, as no specific workarounds are provided.
- agent/title
- agent/references
- agent/weakness
- agent/description
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/source
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/payara
- canonical/payara payara server
- canonical/payara micro