dbcve.org
E RecordsApplication · Oracle

CVE-2021-2393

HIGH · 8.1 CVSS v3.1 Published 2021-07-21
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
See remediation →
87/100
Remediation priority · High
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 Oracle E-Records product of Oracle E-Business Suite (component: E-signatures). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.10. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle E-Records. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle E-Records accessible data as well as unauthorized access to critical data or complete access to all Oracle E-Records accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 confidence

Oracle E-Records E-signatures component allows low-privileged attackers with network access to create, delete, or modify critical data, and gain unauthorized access to all E-Records data due to missing or insufficient authorization controls in the E-signature functionality.

MitigationApply Oracle Critical Patch Update (CPU) for July 2021 or later. Restrict network access to Oracle E-Business Suite to authorized users only. Review and audit user privileges in Oracle E-Records.

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
E RecordsApplication
Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify Oracle E-Records module is installed
    Check if the Oracle E-Records component is installed in your Oracle E-Business Suite environment. This can be verified through Oracle Application Manager (OAM) or by querying the APPS.AD_BUGS table for E-Records related patches.
    Affected if E-Records module is not present in the environment
  2. Check Oracle E-Records version
    Determine the installed version of Oracle E-Records. In Oracle E-Business Suite, this can be checked via the Oracle Application Manager console or by querying the version from the E-Records product family. Compare the installed version against the affected ranges: 12.1.1 through 12.1.3, or 12.2.3 through 12.2.10.
    Affected if The installed version falls within 12.1.1 to 12.1.3 or 12.2.3 to 12.2.10
  3. Confirm E-signature functionality is enabled
    Verify that the E-signature feature within Oracle E-Records is enabled and accessible. This can be checked through the E-Records administration console or by reviewing the E-Records configuration settings that control E-signature access.
    Affected if E-signature functionality is enabled and accessible to users
  4. Verify network accessibility of E-signature interface
    Confirm that the E-signature interface is accessible over the network. Check if Oracle E-Records E-signature URLs are exposed and reachable from the network, as the vulnerability requires network access by low-privileged attackers.
    Affected if The E-signature interface is network-accessible without proper restrictions

Your environment is affected if Oracle E-Records with E-signature functionality is installed, the version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10, and the E-signature interface is enabled and network-accessible.

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.

From vendor data
Upgrade available Upgrade to a release after 12.2.10
Interim mitigation

Apply Oracle Critical Patch Update (CPU) for July 2021 or later. Restrict network access to Oracle E-Business Suite to authorized users only. Review and audit user privileges in Oracle E-Records.

Fix this in E Records Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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