CVE-2021-2373
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 · uneditedVulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Web Runtime). Supported versions that are affected are 9.2.5.3 and Prior. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in JD Edwards EnterpriseOne Tools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of JD Edwards EnterpriseOne Tools accessible data as well as unauthorized read access to a subset of JD Edwards EnterpriseOne Tools accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 · moderate confidenceThis is an access control vulnerability in JD Edwards EnterpriseOne Tools Web Runtime component that allows low-privileged authenticated attackers via HTTP to perform unauthorized read, insert, update, and delete operations on a subset of accessible data. The attack requires human interaction and may impact additional products due to scope change.
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>= 9.2.0.0, <= 9.2.5.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify JD Edwards EnterpriseOne Tools installationCheck the system for Oracle JD Edwards EnterpriseOne Tools installation. Look for installation directories (typically under Oracle product directories) and verify the presence of EnterpriseOne Tools components.Affected if The product is not installed or only older versions (< 9.2.0.0) are present, the system is not affected.
-
Determine installed EnterpriseOne Tools versionUse Oracle system management tools or check version information in the installation directory. Common locations include the Oracle Inventory or version manifest files within the Tools directory.Affected if The installed version falls within the range >= 9.2.0.0 and <= 9.2.5.3, proceed to next checks.
-
Confirm Web Runtime component is enabledInspect the EnterpriseOne Tools configuration to determine if the Web Runtime (HTML/Web-based interfaces) is deployed and active. Check web server configurations and deployed WAR files for Web Runtime components.Affected if Web Runtime is not deployed or disabled, the specific attack vector may not be applicable.
-
Verify HTTP accessibility of Web RuntimeCheck network configuration, load balancer settings, and web server bindings to determine if the Web Runtime interfaces are accessible via HTTP/HTTPS from the network.Affected if Web Runtime is accessible over the network, the vulnerability can be exploited by remote attackers.
-
Review access control configuration for Web RuntimeExamine the Web Runtime security configuration and role-based access control (RBAC) settings to verify if additional authorization layers beyond basic authentication are implemented.Affected if Only basic authentication is required without granular authorization controls on Web Runtime operations, the vulnerability is exploitable.
The environment is affected if JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.5.3 is installed with the Web Runtime component enabled and accessible over the network without additional authorization controls.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Oracle Critical Patch Update (CPU) for July 2021 or subsequent patches that address CVE-2021-2373. Restrict network access to Web Runtime interfaces and implement additional authorization checks.
- Consultation4.0 h
- Implementation3.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2373 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-2373 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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