CVE-2000-0558
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 · uneditedBuffer overflow in HP Openview Network Node Manager 6.1 allows remote attackers to execute arbitrary commands via the Alarm service (OVALARMSRV) on port 2345.
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 · high confidenceBuffer overflow vulnerability in HP Openview Network Node Manager 6.1 allows remote attackers to execute arbitrary commands through the Alarm service (OVALARMSRV) listening on port 2345. The overflow occurs due to insufficient bounds checking in the alarm handling functionality, enabling complete system compromise.
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= 6.1CVSS 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 HP OpenView NNM installation versionLocate and inspect the HP OpenView Network Node Manager installation directory, typically found under /opt/OV or C:\Program Files\HP OpenView. Check for version files or use the ovstatus command if available to display the installed version.Affected if The installed version is HP OpenView Network Node Manager 6.1 exactly.
-
Verify OVALARMSRV service is runningCheck for the OVALARMSRV process using system utilities such as ps on Unix/Linux systems or Task Manager/Tasklist on Windows. This service is the Alarm service component of HP OpenView NNM.Affected if The OVALARMSRV process is active and running on the system.
-
Confirm port 2345 is listeningUse network inspection tools such as netstat, ss, or nmap to verify that port 2345 is in a LISTEN or OPEN state on the server where HP OpenView NNM is installed.Affected if Port 2345 is open and listening, indicating the Alarm service is accessible.
-
Assess network exposure of the serviceDetermine if port 2345 is accessible from network segments outside the trusted internal network by reviewing firewall rules, ACLs, or performing a port scan from an external vantage point.Affected if Port 2345 is reachable from untrusted network segments, exposing the vulnerable service to remote attackers.
A system is affected if it runs HP OpenView Network Node Manager version 6.1 with the OVALARMSRV service listening on port 2345 and that port is network-accessible to untrusted parties.
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 HP security patches for this vulnerability; if patches are unavailable for this older version, upgrade to a supported version of HP Openview NNM or implement network segmentation to restrict unauthorized access to port 2345.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0558 — 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-2000-0558 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