CVE-2022-45129 json
Payara, when deployed to the root context, allows attackers to visit META-INF and WEB-INF
published 3y ago modified 4mo ago also GHSA-q35w-85pq-rv3x , EUVD-2022-48046
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven fish.payara.distributions:payara 5.2022.5, 6.2022.2
- payara payara 4.1.2.191.38, 5.45.0, 5.2022.4, 6.2022.1
Is CVE-2022-45129 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/169864/Payara-Platform-Path-Traversal.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | fish.payara.distributions:payara | >=6.2021.1.Alpha1, <6.2022.2 >=5.0.0.Alpha1, <5.2022.5 <=4.1.2.181 |
6.2022.2 5.2022.5 |
Classification
- Weakness
-
- CWE-552 Files or Directories Accessible to External Parties
References
-
github.com
/payara/Payara/commit/cccdfddeda71c78ae7b3179db5429e1bb8a56b2e
web, patch, third-party-advisory
-
packetstormsecurity.com
/files/169864/Payara-Platform-Path-Traversal.html
web, exploit, third-party-advisory, vdb-entry
-
blog.payara.fish
/whats-new-in-the-november-2022-payara-platform-release
web, release-notes, vendor-advisory
-
docs.payara.fish
/enterprise/docs/Release%20Notes/Release%20Notes%205.45.0.html
web, release-notes, vendor-advisory
-
docs.payara.fish
/community/docs/Release%20Notes/Release%20Notes%205.2022.4.html
web, release-notes, vendor-advisory
-
docs.payara.fish
/community/docs/6.2022.1/Release%20Notes/Release%20Notes%206.2022.1.html
web, release-notes, vendor-advisory
-
seclists.org
/fulldisclosure/2022/Nov/11
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-45129
advisory
-
github.com
/payara/Payara/issues/6136
web
-
github.com
/payara/Payara
package
-
github.com
/payara/Payara/issues?q=FISH-6775
web
Sources
- CVE List CVE-2022-45129
- GitHub Advisory GHSA-q35w-85pq-rv3x
- NVD CVE-2022-45129
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.