CVE-2022-45129
A public proof of concept exists; no exploitation attested.
- Published2022-11-10
- Fixed in6.2022.1 · 5.2022.4 · 5.45.0 · 4.1.2.191.38
- WeaknessCWE-552
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2022-11-1006:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.x | ≥ 6.0.0, < 6.2022.1 | 6.2022.1 | NVD |
| 5.x | ≥ 5.0.0, < 5.2022.4 | 5.2022.4 | NVD |
| 5.45 | < 5.45.0 | 5.45.0 | NVD |
| 4.1 | < 4.1.2.191.38 | 4.1.2.191.38 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.x | ≥ 6.2021.1.Alpha1, < 6.2022.2 | 6.2022.2 | OSV |
| 5.x | ≥ 5.0.0.Alpha1, < 5.2022.5 | 5.2022.5 | OSV |
| 4.1 | ≤ 4.1.2.181 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Payara to 6.2022.1 · 5.2022.4 · 5.45.0 · 4.1.2.191.38
Advisories and patches
- blog.payara.fishRelease Notes · Vendor Advisory
- docs.payara.fishRelease Notes · Vendor Advisory
- docs.payara.fishRelease Notes · Vendor Advisory
- docs.payara.fishRelease Notes · Vendor Advisory
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2025-05-01
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionpoc2025-05-01
- CISA-ADPCVSS 3.17.52025-05-01
- NVDCVSS 3.17.5read 2026-10-23
- CISA-ADPweakness (CWE)CWE-5522025-05-01
- NVDweakness (CWE)CWE-552read 2026-10-23
- FIRST EPSSEPSS score1.9 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2025-09-04
Identifiers
- EUVD-2022-48046same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-q35w-85pq-rv3xsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2022-11-10
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-q35w-85pq-rv3x
Frequently asked questions
What is CVE-2022-45129?
Is CVE-2022-45129 actively exploited?
What is the CVSS score for CVE-2022-45129?
Running payara? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-q35w-85pq-rv3x
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0