Application ServerApplication · Oracle

CVE-2006-5355

HIGH · 10.0 CVSS v2.0 Published 2006-10-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Oracle Single Sign-On component in Oracle Application Server 9.0.4.3, 10.1.2.0.2, and 10.1.2.1.0, Collaboration Suite 9.0.4.2 and 10.1.2, and Oracle E-Business Suite and Applications 11.5.10CU2 has unknown impact and remote attack vectors, aka Vuln# SSO01.

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

A detailed technical summary for this CVE is being prepared.

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= 10.1.2.1.0
Collaboration SuiteApplication
Affected:= 9.0.4.2= 10.1.2
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
Complete
Integrity
Complete
Availability
Complete

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

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.

dbcve · scoped
Patch available Apply the vendor patch
Recommended fix Moderate confidence

Migrate to Oracle Identity Management 11g or higher with Oracle Access Manager; for E-Business Suite, upgrade to EBS 12.2.x (currently supported)

  1. 1. Identify all Oracle Application Server, Collaboration Suite, and E-Business Suite instances running the affected versions (9.0.4.x, 10.1.2.x, 11.5.10CU2).
  2. 2. Oracle Single Sign-On 9.x and 10.x are end-of-life. Plan migration to Oracle Access Manager (OAM) or Oracle Identity Management.
  3. 3. For Oracle E-Business Suite 11.5.10, migrate to Oracle E-Business Suite 12.x or higher, which has modernized SSO using Oracle Access Manager.
  4. 4. Apply the Oracle Critical Patch Update (CPU) from October 2006 or later if staying on legacy versions temporarily - check Oracle Metalink/My Oracle Support for patch 6027086 (SSO01).
  5. 5. Implement network segmentation to limit exposure to the SSO component if immediate upgrade is not feasible.
Caveat Legacy Oracle SSO 9i/10g custom integrations may require re-architecture; EBS 11.5.10 is end-of-life and requires full upgrade path to 12.x

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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