CVE-2023-21993
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 Oracle Clinical Remote Data Capture product of Oracle Health Sciences Applications (component: Forms). The supported version that is affected is 5.4.0.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Clinical Remote Data Capture. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Clinical Remote Data Capture accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 confidenceOracle Clinical Remote Data Capture version 5.4.0.2 contains a vulnerability in the Forms component that allows a low-privileged attacker with network access via HTTP to gain unauthorized access to critical or all data in the system. The vulnerability has high confidentiality impact with no integrity or availability impact, indicating a data exposure/authorization flaw.
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= 5.4.0.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Oracle Clinical Remote Data Capture versionCheck the application version through Oracle Clinical's built-in version information page, typically accessible via the About or Version link in the application footer, or query the Oracle Clinical database version tables if you have administrative accessAffected if The installed version is exactly 5.4.0.2
-
Verify Forms component is deployed and accessibleCheck if the Forms component is deployed on your Oracle Clinical application server by reviewing the application configuration files (such as formsweb.cfg for Oracle Forms) or accessing the Forms servlet URL endpoint typically at /forms/frmservlet or /forms90/frmservletAffected if The Forms component is exposed and accessible via HTTP/HTTPS network access
-
Confirm Forms component is accessible over the networkTest network connectivity to the Forms component URL endpoints (such as /forms/frmservlet or the Oracle Clinical Forms listener port) using curl or a browser from an external or untrusted network segmentAffected if The Forms component is reachable from network locations where low-privileged users operate
-
Review Forms component user permissions and authorization configurationExamine the Oracle Clinical user roles and permissions assigned to the Forms component through the application administration interface, specifically checking whether low-privileged users have access to sensitive data fields or unauthorized record sets within FormsAffected if Low-privileged users have permissions that allow access to critical or all data through the Forms interface
-
Examine application access logs for anomalous Forms data accessReview Oracle HTTP Server access logs, Oracle Forms runtime logs, and Oracle Clinical application logs for patterns where low-privileged users accessed records or data fields outside their expected scopeAffected if Logs show low-privileged users accessing data beyond their authorized scope
Your environment is affected if you are running Oracle Clinical Remote Data Capture version 5.4.0.2 with the Forms component accessible over the network and low-privileged users can access data beyond their authorized scope.
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 the Oracle Critical Patch Update that addresses CVE-2023-21993, or upgrade to a patched version of Oracle Clinical Remote Data Capture if available. If patches are delayed, review and restrict user permissions in the Forms component and implement additional network-level access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-21993 — 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-2023-21993 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