E Business SuiteApplication · Oracle

CVE-2007-3866

HIGH · 7.5 CVSS v2.0 Published 2007-07-18
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
Multiple unspecified vulnerabilities in Oracle E-Business Suite 11.5.10CU2 and 12.0.1 allow remote attackers to have an unknown impact via (a) Oracle Configurator (APPS02), (b) Oracle iExpenses (APPS03), (c) Oracle Application Object Library (APPS09), and (1) APPS12, (2) APPS13, and (3) APPS14 in (d) Oracle Payables.

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

Multiple unspecified vulnerabilities in Oracle E-Business Suite versions 11.5.10CU2 and 12.0.1 affecting Oracle Configurator, iExpenses, Application Object Library, and Payables modules allow remote attackers to cause unknown impact via unspecified vectors.

MitigationApply the July 2007 Oracle Critical Patch Update (CPU) addressing these vulnerabilities, and strongly consider upgrading to a supported Oracle E-Business Suite version as 11.5.10 and 12.0.x are long-end-of-lifed.

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
E Business SuiteApplication
Affected:= 11.5.10.2= 12.0.1

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
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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 Oracle E-Business Suite version
    Query the Oracle database for the current EBS version using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the login page footer which displays the version.
    Affected if The version returned is exactly 11.5.10.2 or 12.0.1 (not a later patch level)
  2. Verify Configurator module installation
    Query the Oracle EBS modules table: SELECT patch_level FROM apps.fnd_application WHERE application_name = 'Oracle Configurator';
    Affected if The Configurator module is installed (patch_level is not null) on an affected EBS version
  3. Verify iExpenses module installation
    Query the Oracle EBS modules table: SELECT patch_level FROM apps.fnd_application WHERE application_name = 'iExpenses';
    Affected if The iExpenses module is installed (patch_level is not null) on an affected EBS version
  4. Verify Application Object Library installation
    Query the Oracle EBS modules table: SELECT patch_level FROM apps.fnd_application WHERE application_name = 'Application Object Library';
    Affected if The Application Object Library is installed (patch_level is not null) on an affected EBS version
  5. Verify Payables module installation
    Query the Oracle EBS modules table: SELECT patch_level FROM apps.fnd_application WHERE application_name = 'Payables';
    Affected if The Payables module is installed (patch_level is not null) on an affected EBS version

You are affected if your Oracle E-Business Suite version is exactly 11.5.10.2 or 12.0.1 and any of the affected modules (Configurator, iExpenses, Application Object Library, or Payables) are installed and 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 the July 2007 Oracle Critical Patch Update (CPU) addressing these vulnerabilities, and strongly consider upgrading to a supported Oracle E-Business Suite version as 11.5.10 and 12.0.x are long-end-of-lifed.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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