CVE-2022-37422
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPayara through 5.2022.2 allows directory traversal without authentication. This affects Payara Server, Payara Micro, and Payara Server Embedded.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePayara through version 5.2022.2 contains an unauthenticated directory traversal vulnerability that allows remote attackers to access files outside the web root directory via specially crafted HTTP requests. This affects Payara Server, Payara Micro, and Payara Server Embedded.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.1.2.191.36< 5.2022.3>= 5.0.0, < 5.42.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Payara versionCheck the version by examining the Payara JAR or WAR manifest, or use the asadmin version command if you have CLI access. Check files such as payara.jar, manifest.mf in the installation directory, or the admin console footer for the version number.Affected if The version number is less than 4.1.2.191.36, less than 5.2022.3, or falls between 5.0.0 and 5.42.0 (exclusive of 5.42.0).
-
Identify Payara edition typeConfirm whether the installation is Payara Server, Payara Micro, or Payara Server Embedded. Check the JAR filename or deployment artifacts for the specific edition.Affected if The affected installation is any of these three editions running the vulnerable versions identified in step 1.
-
Verify HTTP service exposureCheck if the Payara HTTP listener is exposed to network access. Review the network binding configuration in domain.xml or the --port or --httpPort options used when starting Payara. Determine if the HTTP ports are bindable to non-localhost interfaces.Affected if The HTTP service is accessible from network interfaces other than localhost, making the unauthenticated directory traversal exploitable by remote attackers.
You are affected if your Payara installation version falls within the vulnerable ranges and the HTTP service is accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.1.2.191.365.42.05.2022.3
Upgrade Payara to a version beyond 5.2022.2 that contains the security patch for this vulnerability, or apply vendor-supplied patches if available.
Payara 4.1.2.191.36+ or Payara 5.2022.3+ (preferably 5.42.0 or latest stable)
- Identify current Payara version by checking the administration console or server logs
- For Payara 4.x: Plan upgrade to version 4.1.2.191.36 or later stable release
- For Payara 5.x: Plan upgrade to version 5.2022.3 or later (recommended 5.42.0+)
- Review Payara migration guides for version-specific upgrade procedures
- Test the upgrade in a non-production environment first
- Back up all configuration files and application data
- Perform the upgrade following Payara's official upgrade documentation
- Verify the path traversal vulnerability is resolved by testing the vulnerable endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-37422 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data