Fusion MiddlewareApplication · Oracle

CVE-2024-21190

HIGH · 7.5 CVSS v3.1 Published 2024-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Global Lifecycle Management FMW Installer product of Oracle Fusion Middleware (component: Cloning). The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via SFTP to compromise Oracle Global Lifecycle Management FMW Installer. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Global Lifecycle Management FMW Installer accessible data. CVSS 3.1 Base Score 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 · high confidence

Vulnerability in Oracle FMW Installer's cloning component allows unauthenticated network attackers via SFTP to create, delete, or modify critical data. The CVSS vector (PR:N, AV:N, I:H) indicates the cloning SFTP endpoint lacks proper authentication, enabling unauthorized integrity modifications to installer data.

MitigationApply Oracle Critical Patch Update when available; until then, restrict network access to SFTP port used by FMW Installer, disable cloning if not required, and monitor for unauthorized access.

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
Fusion MiddlewareApplication
Affected:= 12.2.1.4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm Oracle FMW version
    Run 'opatch lspatches' or check inventory.xml in $ORACLE_HOME/oraInst.loc for Oracle Fusion Middleware version 12.2.1.4.0
    Affected if Version 12.2.1.4.0 is installed
  2. Identify FMW Installer cloning component
    Check if the FMW Installer is present: look for 'frmw_install' or 'installer' directories under $ORACLE_HOME, or check for FMwInstaller processes
    Affected if FMW Installer cloning component exists in the environment
  3. Locate SFTP port configuration
    Check FMW Installer configuration files (e.g., in inventory or installer home) for SFTP port settings, typically port 22 or custom SFTP port
    Affected if SFTP service is configured for FMW Installer cloning
  4. Verify SFTP service is listening
    Run 'netstat -an | grep -i sftp' or 'ss -tlnp | grep sftp' to identify if SFTP port used by FMW Installer is actively listening
    Affected if SFTP port for FMW Installer is in LISTEN state
  5. Assess network exposure
    Review firewall rules or run 'nmap -p <sftp_port> <localhost>' to confirm if SFTP port is exposed to network
    Affected if SFTP port is accessible from network (not bound to localhost only)

User is affected if Oracle FMW version 12.2.1.4.0 is installed with FMW Installer cloning enabled and its SFTP port is exposed to the network.

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 when available; until then, restrict network access to SFTP port used by FMW Installer, disable cloning if not required, and monitor for unauthorized access.

Fix this in Fusion Middleware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21190 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