| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Payara Community and Enterprise. It has been declared as problematic. This affects an unknown function. The manipulation results in an unknown weakness. This vulnerability was named CVE-2022-45129. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Payara Community and Enterprise (version now known). CWE is classifying the issue as CWE-552. The product makes files or directories accessible to unauthorized actors, even though they should not be. The impact remains unknown. CVE summarizes:
Payara before 2022-11-04, when deployed to the root context, allows attackers to visit META-INF and WEB-INF, a different vulnerability than CVE-2022-37422. This affects Payara Platform Community before 4.1.2.191.38, 5.x before 5.2022.4, and 6.x before 6.2022.1, and Payara Platform Enterprise before 5.45.0.
The weakness was presented 11/10/2022 as cccdfddeda71c78ae7b3179db5429e1bb8a56b2e. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2022-45129 since 11/10/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1083.
Upgrading eliminates this vulnerability. Applying the patch cccdfddeda71c78ae7b3179db5429e1bb8a56b2e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: File accessCWE: CWE-552 / CWE-425
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: 🔍
Patch: cccdfddeda71c78ae7b3179db5429e1bb8a56b2e
Timeline
11/10/2022 🔍11/10/2022 🔍
11/10/2022 🔍
12/11/2022 🔍
Sources
Advisory: cccdfddeda71c78ae7b3179db5429e1bb8a56b2eStatus: Confirmed
CVE: CVE-2022-45129 (🔍)
GCVE (CVE): GCVE-0-2022-45129
GCVE (VulDB): GCVE-100-213408
Entry
Created: 11/10/2022 22:37Updated: 12/11/2022 17:19
Changes: 11/10/2022 22:37 (38), 12/11/2022 17:19 (12)
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.