dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2024-10234

HIGH · 7.3 CVSS v3.1 Published 2024-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable

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 vulnerability was found in Wildfly, where a user may perform Cross-site scripting in the Wildfly deployment system. This flaw allows an attacker or insider to execute a deployment with a malicious payload, which could trigger undesired behavior against the server.

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 a Cross-site scripting (XSS) vulnerability in Wildfly's deployment system where malicious payloads can be injected through the deployment mechanism. The server does not properly sanitize deployment-related inputs, allowing an attacker to execute arbitrary JavaScript or HTML in the context of the Wildfly management interface.

MitigationImplement proper input validation and output encoding on all deployment-related fields and metadata. Sanitize any user-controlled input before rendering it in web interfaces or storing it for later use.

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
Build Of KeycloakApplication
Affected:all versions
Jboss Enterprise Application PlatformApplication
Affected:= 8.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 the installed Wildfly/JBoss EAP or Keycloak product and version
    Locate the version file or startup banner. For JBoss EAP 8.0, check the $JBOSS_HOME/bin/launch.sh or the pom.xml in the installation directory. For Redhat Build of Keycloak, check the version using the server startup logs or the $KEYCLOAK_HOME/bin/kc.sh version command.
    Affected if The installed product is Redhat Build of Keycloak (any version) or JBoss Enterprise Application Platform version 8.0, and the management interface is accessible.
  2. Verify if the Wildfly/JBoss management interface is exposed
    Check the standalone.xml or domain.xml configuration file for management interface bindings. Look for <interface name="management"> sections and verify if the http-interface is bound to a publicly accessible network address (0.0.0.0 or external IP rather than 127.0.0.1).
    Affected if The management HTTP interface is bound to a non-localhost address, making it network-accessible.
  3. Review deployment logs for suspicious payload patterns
    Examine the server.log file (typically in $JBOSS_HOME/standalone/log/ or $KEYCLOAK_HOME/data/log/) for deployment operations. Search for deployment names containing unusual characters like <script>, javascript:, onerror=, or other HTML/JavaScript patterns that could indicate XSS injection attempts.
    Affected if Deployment logs contain suspicious strings that appear to be XSS payloads in deployment names or metadata.
  4. Inspect the management console for injected content
    Access the Wildfly/JBoss management console (typically at http://hostname:9990/ or http://hostname:8080/console) and navigate to the Runtime > Deployments section. Look for deployment names that contain visible script tags, encoded characters, or unexpected HTML fragments.
    Affected if The deployments list in the management console displays deployment names containing script tags, HTML elements, or other unexpected content that could execute in the browser context.

You are affected if you are running Redhat Build of Keycloak (any version) or JBoss Enterprise Application Platform 8.0, and the management interface is network-accessible or you find suspicious XSS patterns in deployment names or logs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on all deployment-related fields and metadata. Sanitize any user-controlled input before rendering it in web interfaces or storing it for later use.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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