CVE-2005-4654
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 · uneditedMultiple unspecified vulnerabilities in Oracle for OpenView (OfO) 8.1.7, 9.1.01, and 9.2, and OfO for Linux, allow remote attackers to have an unknown impact via unknown attack vectors. NOTE: because of the lack of details in the vendor advisory, it is unclear which set of existing CVEs this advisory might refer to.
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 confidenceInsufficient details available. The CVE describes 'multiple unspecified vulnerabilities' in Oracle for OpenView versions 8.1.7, 9.1.01, and 9.2 with unknown impact and unknown attack vectors. The official description explicitly states it is unclear which existing CVEs this advisory might refer to.
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.1.7= 9.1.01= 9.2CVSS 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
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HP Oracle For OpenView is installedCheck for the presence of HP Oracle For OpenView software on the system. On Windows, look in Add/Remove Programs or check for the installation directory. On Unix/Linux, check common installation paths like /opt/hp/oracle or /opt/oracle, or use commands like 'ls -la' on typical installation directories.Affected if The software is present on the system
-
Identify installed versionLocate version information for the installation. Check the About dialog within the application, look for a version file in the installation directory, or examine registry entries on Windows. On Unix/Linux, check for a version file or use package management commands if installed via packages.Affected if The installed version matches 8.1.7, 9.1.01, or 9.2 exactly
-
Verify product is running or enabledCheck if the Oracle For OpenView service or daemon is currently running. On Windows, open Services and look for Oracle For OpenView services. On Unix/Linux, use commands like 'ps aux | grep -i oracle' or 'systemctl status' to check if related processes are active.Affected if The service is running and accessible on the network or locally
If HP Oracle For OpenView version 8.1.7, 9.1.01, or 9.2 is installed and running, the environment is potentially affected by this advisory since the specific vulnerabilities remain undefined but the software version matches the reported affected versions.
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 dataContact Oracle support for specific patch information; if patches are unavailable for this end-of-life software, consider migration to supported Oracle management solutions.
- Consultation2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4654 — 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-4654 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