dbcve.org
Health Sciences InformApplication · Oracle

CVE-2023-21924

MEDIUM · 5.9 CVSS v3.1 Published 2023-04-18
Fix available
A fix is available. Upgrade to 6.3.1.3 or later.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable Patch available

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 Health Sciences InForm product of Oracle Health Sciences Applications (component: Core). Supported versions that are affected are Prior to 6.3.1.3 and Prior to 7.0.0.1. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Health Sciences InForm. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Health Sciences InForm, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Health Sciences InForm accessible data as well as unauthorized read access to a subset of Oracle Health Sciences InForm accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Health Sciences InForm. CVSS 3.1 Base Score 5.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L).

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

A detailed technical summary for this CVE is being prepared.

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
Health Sciences InformApplication
Affected:< 6.3.1.3= 7.0.0.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
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

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 6.3.1.3 or later
Fixed in 6.3.1.3
Vendor patch www.oracle.com →
Recommended fix High confidence

Upgrade to 6.3.1.3 (for versions < 6.3.1.3) or 7.0.0.1 (for version 7.0.0.0)

  1. 1. Identify the current installed version of Oracle Health Sciences InForm by checking the application version in the administration console or system information.
  2. 2. Determine the appropriate upgrade target: if current version is < 6.3.1.3, upgrade to 6.3.1.3; if current version is exactly 7.0.0.0, upgrade to 7.0.0.1.
  3. 3. Review Oracle Critical Patch Update Advisory April 2023 (https://www.oracle.com/security-alerts/cpuapr2023.html) for complete patch details and any additional requirements.
  4. 4. Create a complete backup of the current InForm database and application configuration.
  5. 5. Set up a staging/non-production environment with the same version as production for upgrade testing.
  6. 6. Execute the upgrade following Oracle's official upgrade documentation for InForm 6.3.x or 7.0.x path as applicable.
  7. 7. After upgrade, verify the InForm version reflects the patched release (6.3.1.3 or 7.0.0.1).
  8. 8. Test critical workflows including user authentication, data submission, and reporting to ensure functionality is intact.
Caveat Review Oracle upgrade documentation for version-specific changes; potential impacts to custom integrations, third-party integrations, and workflow configurations should be validated in staging before production deployment.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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