dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21508

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

A denial-of-service vulnerability exists in the Web Runtime SEC component of JD Edwards EnterpriseOne Tools. An authenticated low-privilege attacker can send specially crafted HTTP requests to cause the application to hang or crash repeatedly.

MitigationApply Oracle's patch for JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. If immediate patching is not possible, restrict network access to the Web Runtime interfaces to trusted sources only.

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 installed JD Edwards EnterpriseOne Tools version
    Locate the Tools installation directory and check the version manifest or use Oracle's version checking utilities. Common paths include $JDE_HOME/system/vashmc or check the installer log files.
    Affected if Installed version is lower than 9.2.9.0
  2. Confirm Web Runtime SEC component is configured
    Examine the Web Runtime configuration files in the JD Edwards deployment, typically found in the Web Runtime configuration directories. Look for SEC (Security) component configuration settings.
    Affected if Web Runtime SEC component is present and configured in the environment
  3. Verify network accessibility to Web Runtime interfaces
    Review network firewall rules, load balancer configurations, or web server access controls that govern access to the Web Runtime HTTP endpoints. Check if these interfaces are exposed to untrusted networks.
    Affected if Web Runtime HTTP ports (typically 8080, 8443 or custom ports) are accessible from untrusted or public networks
  4. Inspect logs for repeated hangs or crashes
    Review Web Runtime server logs and HTTP access logs for patterns of application hangs, crashes, or abnormal termination events, particularly those correlating to specific HTTP request patterns.
    Affected if Logs show repeated hanging or crashing behavior of the Web Runtime component

Environment is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.0 AND Web Runtime SEC component is enabled and accessible to authenticated low-privilege users.

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 for JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. If immediate patching is not possible, restrict network access to the Web Runtime interfaces to trusted sources only.

Recommended fix Moderate confidence

9.2.9.0

  1. Review the Oracle JD Edwards EnterpriseOne Tools 9.2.9.0 release notes and upgrade documentation for compatibility requirements
  2. Verify current environment meets prerequisites for upgrading to version 9.2.9.0
  3. Schedule a maintenance window for the upgrade process
  4. Back up the existing JD Edwards EnterpriseOne Tools installation and database
  5. Download Oracle JD Edwards EnterpriseOne Tools version 9.2.9.0 or later from Oracle Support
  6. Follow Oracle's documented upgrade procedure to apply the new version
  7. After upgrade, verify the Web Runtime SEC component is functioning correctly
  8. Monitor system for normal operation and confirm the DoS vulnerability is mitigated

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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