dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2024-56339

HIGH · 7.5 CVSS v3.1 Published 2025-08-07
Fix available
A fix is available. Upgrade to after 25.0.0.7 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
IBM WebSphere Application Server 9.0 and WebSphere Application Server Liberty 17.0.0.3 through 25.0.0.7 could allow a remote attacker to bypass security restrictions caused by a failure to honor security configuration.

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

IBM WebSphere Application Server 9.0 and Liberty versions 17.0.0.3 through 25.0.0.7 contain a vulnerability where the application fails to honor security configuration settings, allowing a remote attacker to bypass security restrictions. This is a security configuration bypass affecting both the traditional and Liberty deployment models.

MitigationApply the IBM-provided patch or update to the affected WebSphere versions and review security configuration settings to ensure proper enforcement of security restrictions.

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
Websphere Application ServerApplication
Affected:>= 17.0.0.3, <= 25.0.0.7= 9.0.0.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 WebSphere Application Server version
    For traditional WebSphere: check the version via installation directory or admin console. For Liberty: check the version in thewlp/usr/servers/<serverName>/server.env or using the command 'java -jar wlp-api-archive.jar --version'. The version string typically appears as 9.0.x.x for traditional or 17.0.0.3 through 25.0.0.x for Liberty.
    Affected if The installed version falls within 17.0.0.3 to 25.0.0.7 inclusive, or equals exactly 9.0.0.0 for traditional WebSphere Application Server.
  2. Confirm deployment model
    Determine whether the deployment uses traditional WebSphere Application Server or WebSphere Liberty by checking the installation structure. Traditional uses WebSphere/AppServer directory structure with profiles; Liberty uses wlp/usr/servers/<serverName> structure.
    Affected if Either deployment model is in use with an affected version.
  3. Verify security configuration exists
    For traditional WebSphere: navigate to Security > Global Security in the admin console, or check the security.xml file in the config directory. For Liberty: check the server.xml for <feature>security</feature> or <feature>appSecurity</feature> elements and associated authorization settings.
    Affected if Security features are configured and enabled in the environment.
  4. Inspect security configuration settings
    Review the configured security settings for potential bypass vectors. For traditional: check security.xml and policy files. For Liberty: review server.xml for security-related elements including authentication, authorization, and role mappings.
    Affected if Security configuration is present but the environment runs an affected version, indicating potential for configuration bypass.

A user is affected if their WebSphere Application Server (traditional or Liberty) version is 9.0.0.0 or falls within 17.0.0.3 through 25.0.0.7 AND security configuration is enabled in the deployment.

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 a release after 25.0.0.7
Interim mitigation

Apply the IBM-provided patch or update to the affected WebSphere versions and review security configuration settings to ensure proper enforcement of security restrictions.

Recommended fix High confidence

WebSphere Application Server Liberty 25.0.0.8 or later; WebSphere Application Server traditional 9.0.x latest security patch

  1. 1. Identify the specific WebSphere Application Server edition and version currently installed (Liberty or traditional)
  2. 2. For WebSphere Application Server Liberty: Upgrade to version 25.0.0.8 or later
  3. 3. For WebSphere Application Server traditional 9.0.x: Apply the latest available security patch from IBM Fix Central
  4. 4. After upgrading, verify the security configuration is properly honored by reviewing the server.xml and server-specific configuration files
  5. 5. Test that security restrictions function as expected after the upgrade
  6. 6. Monitor IBM Security Bulletins for any further updates
Caveat Review IBM migration guides for any configuration or API changes between versions; some deprecated features may require updates

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

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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