dbcve.org
WildflyApplication · Redhat

CVE-2022-1278

HIGH · 7.5 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to 27.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A flaw was found in WildFly, where an attacker can see deployment names, endpoints, and any other data the trace payload may contain.

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 confidence

This is an information disclosure vulnerability in WildFly where trace-level logging exposes sensitive deployment metadata. An unauthenticated remote attacker can view deployment names, endpoint structures, and any other data contained in trace log payloads, revealing internal infrastructure details that could aid in further attacks.

MitigationRestrict or disable trace-level logging in production environments, secure access to WildFly logging infrastructure, and ensure trace logs are not exposed to unauthenticated users or network paths.

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
WildflyApplication
Affected:< 27.0.0
AmqApplication
Affected:= 2.0
Amq OnlineApplication
Affected:all versions
Integration Camel KApplication
Affected:all versions
Integration Service RegistryApplication
Affected:all versions
Jboss A MqApplication
Affected:= 7
Jboss Enterprise Application Platform Expansion PackApplication
Affected:all versions
Single Sign OnApplication
Affected:= 7.0

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
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 checks

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

  1. Identify WildFly version
    Check the installed WildFly version against the affected range. For WildFly Core, examine the version manifest or running instance banner. For derived products like Red Hat AMQ, JBoss AMQ, or SSO, locate the bundled WildFly version in product-specific metadata or startup logs.
    Affected if Installed WildFly version is earlier than 27.0.0, or the product is one of the listed Red Hat products (AMQ 2.0, AMQ Online, Camel K, Service Registry, JBoss AMQ 7, EAP Expansion Pack, SSO 7.0) which bundle vulnerable WildFly versions
  2. Verify trace-level logging configuration
    Inspect the WildFly logging subsystem configuration. Check logging profile settings and the standalone.xml (or domain.xml) configuration file for any logger definitions set to TRACE level, particularly those related to deployment or endpoint processing.
    Affected if Trace-level logging is enabled for any logger related to deployment metadata, endpoint structures, or web-service processing
  3. Confirm logging output exposure
    Review where trace logs are written and how they are accessed. Check file permissions on log directories, verify whether logging endpoints or APIs are exposed without authentication, and examine network access controls on any log aggregation or management interfaces.
    Affected if Trace logs are readable by unauthenticated users, exposed via unauthenticated network paths, or accessible through management interfaces without proper access controls

A user is affected if they run a vulnerable WildFly-derived product with trace-level logging enabled AND that logging output is accessible to unauthenticated users or network attackers.

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
Upgrade available Upgrade to 27.0.0 or later
Fixed in 27.0.0
Interim mitigation

Restrict or disable trace-level logging in production environments, secure access to WildFly logging infrastructure, and ensure trace logs are not exposed to unauthenticated users or network paths.

Recommended fix High confidence

WildFly 27.0.0 or later

  1. Upgrade WildFly to version 27.0.0 or later to resolve the trace payload exposure vulnerability
  2. After upgrading, verify that trace logging no longer exposes deployment names, endpoints, or other sensitive payload data
  3. Test the upgraded environment to ensure all existing functionality remains intact

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

Fix this in Wildfly Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1278 — 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-2022-1278 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