dbcve.org
HTTP ServerWeb server / proxy · Oracle

CVE-2006-5354

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 HTTP Server 9.2.0.7 and 10.1.0.5, Application Server 9.0.4.3, 10.1.2.0.2, 10.1.2.1.0, and 10.1.3.0, racle 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# OHS06.

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
HTTP ServerWeb server / proxy
Affected:= 9.2.0.7= 10.1.0.5
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
Vendor patch www.securityfocus.com →
Recommended fix High confidence

Migrate to a currently supported Oracle product version (Oracle HTTP Server 10g/11g/12c or later, as these 2006-era versions are long past extended support)

  1. 1. Contact Oracle Support to obtain the specific patch for this vulnerability (referenced in Oracle Critical Patch Update October 2006)
  2. 2. Apply the Oracle HTTP Server patch specific to your version (9.2.0.7 or 10.1.0.5)
  3. 3. Apply patches to affected Application Server installations (9.0.4.3, 10.1.2.0.2, 10.1.2.1.0, 10.1.3.0)
  4. 4. Apply patches to Oracle Collaboration Suite (9.0.4.2, 10.1.2)
  5. 5. Apply patches to Oracle E-Business Suite 11.5.10 CU2
  6. 6. After patching, restart all Oracle HTTP Server and Application Server services
  7. 7. Verify the patch was applied successfully by checking Oracle version outputs
Caveat These are legacy 2006-era products; migration to modern Oracle versions may require application compatibility testing and significant reconfiguration

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-5354 — 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-2006-5354 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