dbcve.org
Application ServerApplication · Oracle

CVE-2007-2130

HIGH · 9.0 CVSS v2.0 Published 2007-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
Unspecified vulnerability in Workflow Cartridge, as used in Oracle Database Server 9.2.0.1, 10.1.0.2, and 10.2.0.1; Application Server 9.0.4.3 and 10.1.2.0.2; Collaboration Suite 10.1.2; and E-Business Suite; has unknown impact and remote authenticated attack vectors, aka OWF01.

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

Unspecified vulnerability in Oracle Workflow Cartridge affecting Database Server, Application Server, Collaboration Suite, and E-Business Suite. Requires remote authenticated access with unknown impact, though CVSS 9 indicates severe consequences.

MitigationApply Oracle Critical Patch Updates (CPUs) containing fixes for OWF01. Oracle released patches for this vulnerability as part of their quarterly security updates. Restrict network access to Oracle Workflow interfaces and remove unnecessary database privileges from affected accounts.

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
Application ServerApplication
Affected:= 9.0.4.3= 10.1.2.0.2
Collaboration SuiteApplication
Affected:= 10.1.2
Database ServerDatabase / datastore
Affected:= 9.2.0.1= 10.1.0.2= 10.2.0.1
E Business SuiteApplication
Affected:all versions

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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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. Identify installed Oracle product and version
    Query the Oracle inventory or registry for installed Oracle products. On Unix systems check /etc/oraInst.loc or the Oracle Inventory directory. On Windows check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE. Use sqlplus to query v$version or dba_registry for database components.
    Affected if The installed product matches one of the affected versions: Application Server 9.0.4.3 or 10.1.2.0.2, Collaboration Suite 10.1.2, Database Server 9.2.0.1, 10.1.0.2, or 10.2.0.1, or any E-Business Suite version.
  2. Confirm Oracle Workflow Cartridge is installed
    Check if the Oracle Workflow component is present. For Database: query DBA_REGISTRY or dba_components for 'OWF' or 'Oracle Workflow'. For Application Server: check the Oracle Application Server inventory for Oracle Workflow Cartridge installation.
    Affected if Oracle Workflow Cartridge (OWF) is listed as an installed component in the Oracle component registry.
  3. Verify Oracle Workflow version
    Query the Oracle Workflow version. For database installations, check the version via the workflow packages or component registry. For application server, check the Oracle Workflow Cartridge version through the application server console or component inventory.
    Affected if The Oracle Workflow Cartridge version matches the affected Oracle product versions listed in the CVE.
  4. Check if Oracle Workflow is enabled and accessible
    Determine if Oracle Workflow services are running and accessible. For Application Server, check if the Workflow container/OC4J instance is active. For Database, check if the WFSQL or other workflow database objects are accessible. Review network accessible endpoints related to /ows/ or /wf/ paths.
    Affected if Oracle Workflow Cartridge is installed, enabled, and network accessible to authenticated users.

You are affected if Oracle Workflow Cartridge is installed and your Oracle product version matches one of the specific versions listed in the affected products, or if you are running any version of Oracle E-Business Suite with Oracle Workflow enabled.

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 Updates (CPUs) containing fixes for OWF01. Oracle released patches for this vulnerability as part of their quarterly security updates. Restrict network access to Oracle Workflow interfaces and remove unnecessary database privileges from affected accounts.

Fix this in Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

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