dbcve.org
Outside In TechnologyApplication · Oracle

CVE-2024-21120

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
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 Outside In Technology product of Oracle Fusion Middleware (component: Outside In Core). Supported versions that are affected are 8.5.6 and 8.5.7. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Outside In Technology executes to compromise Oracle Outside In Technology. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Outside In Technology accessible data as well as unauthorized read access to a subset of Oracle Outside In Technology accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Outside In Technology. CVSS 3.1 Base Score 5.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 · high confidence

Vulnerability in Oracle Outside In Technology (component: Outside In Core) affecting versions 8.5.6 and 8.5.7. Easily exploitable by low-privileged attacker with local logon access, allowing unauthorized read/write/delete access to some accessible data and partial denial of service. Attack vector is local (AV:L), requires low privileges (PR:L), and no user interaction.

MitigationApply Oracle Critical Patch Update for affected versions (8.5.6/8.5.7). If patching is delayed, restrict physical and logical access to systems running Oracle Outside In Technology and follow least-privilege principles.

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
Outside In TechnologyApplication
Affected:= 8.5.6= 8.5.7

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Check if Oracle Outside In Technology is installed
    Look for the Outside In product installation on the system. This is often bundled with Oracle Database, Oracle Fusion Middleware, or Oracle E-Business Suite. Check common Oracle installation directories or use system inventory tools to find Oracle-related software.
    Affected if The product is present on the system and version is 8.5.6 or 8.5.7
  2. Identify the installed version of Outside In Core
    Locate the version information for the Outside In Core component. This is typically found in the component's documentation, readme files, or the installer details. Check the Oracle installation or application that bundles this technology.
    Affected if Installed version equals 8.5.6 or 8.5.7 exactly as specified in the affected versions list
  3. Verify access to the system by low-privileged users
    Review system permissions and access controls. Check if low-privilege accounts (non-admin users) can log on locally to the system where Outside In Technology runs.
    Affected if Low-privileged users have local logon access to the system hosting the vulnerable component
  4. Determine if Outside In Core is actively used or exposed
    Identify whether any application or service on the system utilizes the Outside In Core component for document processing, content extraction, or similar functions.
    Affected if Outside In Core is in use and accessible to local users on the affected system

A system is affected if Oracle Outside In Technology version 8.5.6 or 8.5.7 is installed and low-privileged local users can access that system.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update for affected versions (8.5.6/8.5.7). If patching is delayed, restrict physical and logical access to systems running Oracle Outside In Technology and follow least-privilege principles.

Fix this in Outside In Technology Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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