dbcve.org
Collaboration SuiteApplication · Oracle

CVE-2005-3454

HIGH · 10.0 CVSS v2.0 Published 2005-11-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Collaboration Suite 10g Release 1 version 10.1.1 and 9i Release 2 9.0.4.2 have unknown impact and attack vectors, as identified by Oracle Vuln# (1) OCS01, (2) OCS02, (3) OCS03, and (4) OCS04 for Calendar; (5) OCS05, (6) OCS06, (7) OCS07, (8) OCS08, (9) OCS09, and (10) OCS10 for Email Server; and (11) OCS11, (12) OCS12, and (13) OCS13 for Oracle Files.

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 Collaboration Suite 10g Release 1 (10.1.1) and 9i Release 2 (9.0.4.2) affecting Calendar (OCS01-OCS04), Email Server (OCS05-OCS10), and Oracle Files (OCS11-OCS13) components. The CVSS score of 10 indicates critical severity, though specific impact and attack vectors are not disclosed in the Oracle advisory.

MitigationApply Oracle Critical Patch Updates (CPUs) for 2005 that address these vulnerabilities in Oracle Collaboration Suite. If patching is not feasible, consider network segmentation and restricting access to the Calendar, Email Server, and Oracle Files web interfaces.

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

AV:N/AC:L/Au:N/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 Oracle Collaboration Suite installation
    Check for Oracle Collaboration Suite directories (commonly under $ORACLE_HOME) or look for OCS-related services/processes on the system
    Affected if Oracle Collaboration Suite software is present on the system
  2. Determine installed OCS version
    Use Oracle inventory or check version files: opatch lsinventory, or look for version.txt in OCS home directory. Also check running processes for version strings
    Affected if Version is exactly 9.0.4.2 or 10.1.1
  3. Check if Calendar component is active
    Inspect running web services on ports used by Calendar (typically 80/443 or Oracle-specific ports). Check for Apache/Oracle HTTP Server processes serving Calendar endpoints
    Affected if Calendar web interface is accessible and running on affected version 9.0.4.2 or 10.1.1
  4. Check if Email Server component is active
    Inspect for Oracle Email Server processes (Oracle Collaboration Suite Email) and associated listener ports. Check if webmail or IMAP/POP interfaces are exposed
    Affected if Email Server web interface or mail services are running on affected version 9.0.4.2 or 10.1.1
  5. Check if Oracle Files component is active
    Inspect for Oracle Files web application processes. Check for Oracle Files web interface availability on standard web ports
    Affected if Oracle Files web interface is accessible and running on affected version 9.0.4.2 or 10.1.1

User is affected if Oracle Collaboration Suite version 9.0.4.2 or 10.1.1 is installed AND any of the Calendar, Email Server, or Oracle Files components are enabled and accessible on the network.

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) for 2005 that address these vulnerabilities in Oracle Collaboration Suite. If patching is not feasible, consider network segmentation and restricting access to the Calendar, Email Server, and Oracle Files web interfaces.

Fix this in Collaboration Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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