E Business SuiteApplication · Oracle

CVE-2007-5529

HIGH · 7.5 CVSS v2.0 Published 2007-10-17
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
Unspecified vulnerability in the Oracle Self-Service Web Applications component in client-only installations of Oracle E-Business Suite 11.5.10.2 has unknown impact and remote attack vectors, aka APP08.

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

Vulnerability in Oracle E-Business Suite 11.5.10.2 Self-Service Web Applications component, specifically in client-only installations. The CVSS 7.5 indicates high severity with remote exploit potential, though the exact nature (injection, authentication bypass, etc.) is unspecified in public documentation.

MitigationApply Oracle Critical Patch Update (CPU) from October 2007 or later that addresses APP08. If patching is not feasible, restrict network access to the Self-Service Web Applications tier and review client-only installation configurations for unnecessary exposure.

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

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. Confirm Oracle E-Business Suite version
    Execute SQL query 'SELECT release_name FROM fnd_product_groups;' or check the Oracle Applications login banner for version 11.5.10.2
    Affected if The installed version is exactly 11.5.10.2
  2. Identify Self-Service Web Applications installation
    Query Oracle Application Manager or check the product installation status for the Self-Service Web Applications (SSWA) component via adadmin utility or FND_PRODUCT_INSTALLATIONS table
    Affected if Self-Service Web Applications component is installed
  3. Determine installation type
    Review Oracle E-Business Suite installation documentation or configuration to confirm whether this is a 'client-only' installation versus a standard three-tier installation (database, application, web tier)
    Affected if This is a client-only installation where the Self-Service Web Applications tier may be unnecessarily exposed
  4. Check network accessibility of web tier
    Review network configuration and firewall rules to determine if the Self-Service Web Applications HTTP listener port is accessible from untrusted networks
    Affected if The Self-Service Web Applications tier is exposed to networkaccessible interfaces without proper access controls

A user is affected if they are running Oracle E-Business Suite 11.5.10.2 with Self-Service Web Applications configured as a client-only installation that is network-accessible to untrusted users.

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 (CPU) from October 2007 or later that addresses APP08. If patching is not feasible, restrict network access to the Self-Service Web Applications tier and review client-only installation configurations for unnecessary exposure.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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