dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21514

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 9.2.9.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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: Web Runtime 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 unauthorized read access to a subset of JD Edwards EnterpriseOne Tools accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

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

Unauthenticated information disclosure vulnerability in the Web Runtime SEC component of JD Edwards EnterpriseOne Tools versions prior to 9.2.9.0. Attackers with network access via HTTP can read a subset of accessible data due to insufficient access controls in the Web Runtime.

MitigationApply Oracle patch 9.2.9.0 or later to JD Edwards EnterpriseOne Tools. Until patched, restrict network access to Web Runtime interfaces from untrusted sources.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 JD Edwards EnterpriseOne Tools version
    Locate the installed Tools version through Oracle system administration utilities, installation directories, or version inquiry screens accessible via JD Edwards EnterpriseOne Administrator
    Affected if Installed version is prior to 9.2.9.0 (any version below this threshold)
  2. Confirm Web Runtime component is installed
    Verify the Web Runtime SEC component is present in the JD Edwards EnterpriseOne deployment through Oracle Enterprise Manager or component inventory listing
    Affected if Web Runtime SEC component is installed and part of the deployment
  3. Check Web Runtime HTTP listeners
    Identify HTTP ports and endpoints configured for Web Runtime services in the JD Edwards EnterpriseOne web container configuration files or deployment descriptors
    Affected if HTTP listeners are configured and active for Web Runtime
  4. Assess network exposure of Web Runtime
    Review firewall rules, network ACLs, or load balancer configurations to determine if Web Runtime interfaces are accessible from untrusted network segments
    Affected if Web Runtime HTTP endpoints are reachable from outside the trusted network boundary

Environment is affected if running any JD Edwards EnterpriseOne Tools version below 9.2.9.0 with Web Runtime SEC component exposed to accessible HTTP network interfaces.

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 patch 9.2.9.0 or later to JD Edwards EnterpriseOne Tools. Until patched, restrict network access to Web Runtime interfaces from untrusted sources.

Recommended fix High confidence

9.2.9.0

  1. 1. Review the Oracle JD Edwards EnterpriseOne Tools 9.2.9.0 release notes and patch documentation for upgrade requirements
  2. 2. Ensure you have a complete backup of the current JD Edwards EnterpriseOne Tools environment
  3. 3. Download Oracle JD Edwards EnterpriseOne Tools version 9.2.9.0 or later from Oracle Support
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Apply the upgrade following Oracle's standard installation and configuration procedures
  6. 6. Verify the Web Runtime SEC component is properly updated
  7. 7. Validate that the JD Edwards EnterpriseOne Tools application functions correctly post-upgrade
  8. 8. Confirm the vulnerability is remediated by verifying the patch level

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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