CVE-2005-3466
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 · uneditedUnspecified vulnerability in Enterprise CRM Sales in Oracle 8.81 up to 8.9 has unknown impact and attack vectors, as identified by Oracle Vuln# CRM01.
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 · low confidenceOracle Enterprise CRM Sales versions 8.81 through 8.9 contain an unspecified vulnerability (Oracle Vuln# CRM01) with unknown impact and attack vectors. The CVSS score of 10 indicates critical severity, but the exact nature of the flaw is not disclosed in available documentation.
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<= 8.9= 8.81CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Oracle Peoplesoft Enterprise CRM versionQuery the Oracle application version information through the system console, Oracle Application Manager, or check the installation directory for version manifests. Common commands include checking PS_HOME directory or querying the database for version tables.Affected if The installed version is 8.81, 8.82, 8.83, 8.84, 8.85, 8.86, 8.87, 8.88, 8.89, or 8.9 (any version from 8.81 through 8.9 inclusive).
-
Confirm Oracle Enterprise CRM Sales module is deployedCheck if the Oracle Enterprise CRM Sales component (Sales module) is installed and running within the Peoplesoft Enterprise CRM environment. Review the application module configuration and component list.Affected if The Oracle Enterprise CRM Sales module is present and active in the environment.
-
Determine if the system is network-accessibleVerify network exposure of the Oracle application ports and web interfaces. Check firewall rules and network segmentation around the Oracle servers.Affected if The Oracle CRM application is accessible from network segments beyond the trusted internal network.
-
Check for applied Oracle Critical Patch UpdatesReview Oracle patch inventory by examining the OPatch utility output or checking Oracle Metalink/MOS for applied patches related to CRM01 vulnerability. Query: opatch lsinventoryAffected if No CPU patches from 2005 or later addressing CRM01 have been applied to the system.
The environment is affected if Oracle Peoplesoft Enterprise CRM Sales version 8.81 through 8.9 is installed and the system is accessible, with no Oracle Critical Patch Updates applied for this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Updates (CPUs) from 2005 onward, or migrate to a supported Oracle E-Business Suite version (11i or 12.x) as Oracle E-Business Suite 8.x has been unsupported for many years.
- Consultation8.0 h
- Implementation120.0 h
- Testing40.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $51,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3466 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-3466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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