dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21509

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 9.2.9.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Web Runtime SEC). Supported versions that are affected are Prior to 9.2.9.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

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

A denial of service vulnerability in the JD Edwards EnterpriseOne Tools Web Runtime SEC component allows low-privileged attackers with network access via HTTP to crash or hang the application. The vulnerability affects versions prior to 9.2.9.0 and is easily exploitable.

MitigationApply Oracle's patch by upgrading JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later to address the vulnerability.

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
Jd Edwards Enterpriseone ToolsApplication
Affected:< 9.2.9.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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 JD Edwards EnterpriseOne Tools version
    Locate the Tools installation directory and check the version. The version is typically recorded in the 'jde.ini' or 'jdelog.properties' file in the Tools installation path, or can be retrieved via Oracle Enterprise Manager. Look for a 'Release' or 'ToolsVersion' parameter.
    Affected if The installed version number is lower than 9.2.9.0
  2. Confirm Web Runtime (HTML Server) is enabled
    Check the HTML Server configuration in the JD Edwards EnterpriseOne Administration Console or review the 'jas.ini' file in the Tools web runtime directory. Verify the 'Server' or 'HTML Server' instance is in a running or configured state.
    Affected if The Web Runtime SEC component is installed and accessible over HTTP/HTTPS
  3. Verify network accessibility of Web Runtime
    Attempt to access the Web Runtime endpoint (typically on port 8000 or 8080 for the HTML Server). Use a browser or curl to hit the login page or main endpoint: http://server:port/jde/ or the equivalent path for the EnterpriseOne web client.
    Affected if The Web Runtime is reachable over the network on HTTP/HTTPS ports
  4. Check for recent crashes or hangs
    Review the JD Edwards HTML Server logs (jde.log, jde_CallObject.log) and Web container logs (Oracle WebLogic or Apache) for signs of application hangs, crashes, or unexpected termination events around the time of requests.
    Affected if Logs show repeated crashes, hangs, or unresponsiveness in the Web Runtime SEC component

The environment is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.0 and the Web Runtime SEC component is enabled and accessible over the network.

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 9.2.9.0 or later
Fixed in 9.2.9.0
Interim mitigation

Apply Oracle's patch by upgrading JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later to address the vulnerability.

Recommended fix High confidence

9.2.9.0

  1. Review Oracle JD Edwards EnterpriseOne Tools release notes for version 9.2.9.0 to understand changes and prerequisites
  2. Ensure backup of current JD Edwards EnterpriseOne Tools environment before proceeding
  3. Obtain the JD Edwards EnterpriseOne Tools 9.2.9.0 installation media from Oracle
  4. Follow Oracle's standard upgrade procedure for JD Edwards EnterpriseOne Tools, which typically involves running the installer on the EnterpriseOne server
  5. After upgrade, verify that the Web Runtime SEC component is functioning correctly
  6. Test that the application is accessible and responsive to confirm the DoS vulnerability is resolved
Caveat Review Oracle release notes for 9.2.9.0; specific breaking changes are not detailed in the CVE description

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

Fix this in Jd Edwards Enterpriseone Tools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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