dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21524

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 9.2.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Monitoring and Diagnostics SEC). Supported versions that are affected are Prior to 9.2.9.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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

This is a critical unauthenticated remote code execution vulnerability in Oracle JD Edwards EnterpriseOne Tools, affecting the Monitoring and Diagnostics SEC component. Versions prior to 9.2.9.0 are vulnerable to complete system compromise via HTTP network attacks without any authentication required.

MitigationApply Oracle's official patch by upgrading JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later. Given the critical CVSS score and unauthenticated attack vector, this upgrade should be prioritized urgently.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed JD Edwards EnterpriseOne Tools version using Oracle's standard version detection methods (check Oracle Enterprise Manager, deployment manager, or tools installation directory for version file)
    Affected if The installed version is lower than 9.2.9.0
  2. Confirm Monitoring and Diagnostics SEC component status
    Verify whether the Monitoring and Diagnostics SEC component is provisioned or enabled in the JD Edwards EnterpriseOne environment (check through JD Edwards EnterpriseOne Administration Server or corresponding management console)
    Affected if The Monitoring and Diagnostics SEC component is installed and active
  3. Assess HTTP network exposure
    Determine if the JD Edwards EnterpriseOne web interfaces (HTML Gateway, AIS Server) are exposed to untrusted networks by reviewing network firewall rules and load balancer configurations
    Affected if The HTTP-based interfaces are reachable from untrusted network segments without authentication restrictions
  4. Review web service endpoint exposure
    Inspect exposed HTTP endpoints for the Monitoring and Diagnostics SEC component through web server configuration files or Oracle Enterprise Manager diagnostic outputs
    Affected if Unauthenticated HTTP endpoints for the Monitoring and Diagnostics component are externally accessible

The environment is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.0 AND the Monitoring and Diagnostics SEC component is enabled and accessible via HTTP from an untrusted 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 official patch by upgrading JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later. Given the critical CVSS score and unauthenticated attack vector, this upgrade should be prioritized urgently.

Recommended fix High confidence

9.2.9.0

  1. Back up the current JD Edwards EnterpriseOne Tools installation and database before proceeding with any upgrade.
  2. Review Oracle's official upgrade documentation for JD Edwards EnterpriseOne Tools to understand prerequisites and compatibility requirements.
  3. Download JD Edwards EnterpriseOne Tools version 9.2.9.0 or later from the Oracle Software Delivery Cloud or My Oracle Support.
  4. Apply the upgrade in a non-production environment first to validate compatibility with your existing JD Edwards EnterpriseOne applications and configurations.
  5. Execute the upgrade following Oracle's documented procedures, ensuring all prerequisites are met.
  6. After upgrading, verify that the Monitoring and Diagnostics SEC component is functioning correctly.
  7. Confirm the installation by checking the version number displays as 9.2.9.0 or later.
  8. Test critical business workflows to ensure the upgrade did not introduce regressions.

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

Fix this in Jd Edwards Enterpriseone Tools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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