Payara Server/Micro/Server Embedded up to 5.2022.2 pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Payara Server, Micro and Server Embedded up to 5.2022.2. It has been rated as critical. The affected element is an unknown function. This manipulation causes pathname traversal. This vulnerability appears as CVE-2022-37422. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in Payara Server, Micro and Server Embedded up to 5.2022.2. It has been declared as critical. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Payara through 5.2022.2 allows directory traversal without authentication. This affects Payara Server, Payara Micro, and Payara Server Embedded.
The weakness was presented 08/19/2022. The advisory is shared at blog.payara.fish. This vulnerability is known as CVE-2022-37422 since 08/05/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at blog.payara.fish.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: Pathname traversalCWE: CWE-21 / CWE-22
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: blog.payara.fish
Timeline
08/05/2022 🔍08/19/2022 🔍
08/19/2022 🔍
09/18/2022 🔍
Sources
Advisory: blog.payara.fishStatus: Confirmed
CVE: CVE-2022-37422 (🔍)
GCVE (CVE): GCVE-0-2022-37422
GCVE (VulDB): GCVE-100-206773
Entry
Created: 08/19/2022 10:57Updated: 09/18/2022 12:05
Changes: 08/19/2022 10:57 (39), 09/18/2022 12:05 (11)
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.