dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-8097

MEDIUM · 6.7 CVSS v4.0 Published 2024-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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 · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Payara Platform Payara Server (Logging modules) allows Sensitive credentials posted in plain-text on the server log.This issue affects Payara Server: from 6.0.0 before 6.18.0, from 6.2022.1 before 6.2024.9, from 5.20.0 before 5.67.0, from 5.2020.2 before 5.2022.5, from 4.1.2.191.0 before 4.1.2.191.50.

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 · high confidence

Sensitive credentials are being written in plain-text to Payara Server logs due to improper handling in the logging module. Any unauthorized user with access to server log files can read these credentials.

MitigationUpgrade Payara Server to the fixed versions (6.18.0, 6.2024.9, 5.67.0, 5.2022.5, or 4.1.2.191.50) or later, or configure log formatters to mask sensitive credential data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Local
Complexity
Low
Privileges
High
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Payara Server version
    Locate the Payara Server installation directory. In the root Payara directory, check the 'glassfish' or 'domains' folder structure. The version is typically visible in the Payara Server startup banner or in the 'glassfish/lib/appserv-rt.jar' manifest, or run: asadmin version
    Affected if The installed version is earlier than 6.18.0, 6.2024.9, 5.67.0, 5.2024.5, or 4.1.2.191.50 (or cannot be determined but is known to be Payara Server)
  2. Verify logging module is active
    Check if logging is enabled by inspecting the domain.xml configuration file in $PAYARA_HOME/glassfish/domains/domain1/config/domain.xml. Look for the log-service element or check if the logging.properties file exists in the config directory
    Affected if Logging is enabled (this is the default configuration) - the vulnerability only applies when logging is active
  3. Inspect server log files for plain-text credentials
    Examine log files in $PAYARA_HOME/glassfish/domains/domain1/logs/ directory. Search for patterns that may contain sensitive data such as: password=, pwd=, credential=, token=, secret=, or database connection strings. Use grep or similar to search for these keywords in the log files
    Affected if Log files contain any plain-text sensitive strings that appear to be passwords, credentials, tokens, or secrets used in server configuration or application deployments
  4. Check for sensitive data in server stdout and stderr logs
    Review the server.log, console.log, or any stdout/stderr output files in the logs directory. Look for entries that may contain sensitive information passed during startup, deployment, or runtime operations, particularly around datasources, security realms, or resource creation
    Affected if Sensitive values such as cleartext passwords or credentials appear in any of the standard output or error log files

A user is affected if Payara Server version is below the fixed releases AND logging is enabled AND the log files contain any plain-text sensitive credentials or secrets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Payara Server to the fixed versions (6.18.0, 6.2024.9, 5.67.0, 5.2022.5, or 4.1.2.191.50) or later, or configure log formatters to mask sensitive credential data.

Recommended fix High confidence

6.18.0, 6.2024.9, 5.67.0, 5.2022.5, or 4.1.2.191.50 (depending on current branch)

  1. 1. Identify the currently running Payara Server version using the admin console or version detection
  2. 2. Determine which version branch your current installation falls into based on the affected ranges provided
  3. 3. For Payara 6.x versions from 6.0.0 before 6.18.0: upgrade to version 6.18.0 or later
  4. 4. For Payara 6.x versions from 6.2022.1 before 6.2024.9: upgrade to version 6.2024.9 or later
  5. 5. For Payara 5.x versions from 5.20.0 before 5.67.0: upgrade to version 5.67.0 or later
  6. 6. For Payara 5.x versions from 5.2020.2 before 5.2022.5: upgrade to version 5.2022.5 or later
  7. 7. For Payara 4.x versions from 4.1.2.191.0 before 4.1.2.191.50: upgrade to version 4.1.2.191.50 or later
  8. 8. After upgrade, verify that sensitive credentials are no longer being logged in plain-text
Caveat Review Payara release notes for breaking changes between your current version and the target fixed version; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8097 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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