CVE-2014-2624
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 HP Network Node Manager i (NNMi) 9.0x, 9.1x, and 9.2x allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-2264.
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 confidenceCritical remote code execution vulnerability in HP Network Node Manager i (NNMi) affecting versions 9.0x, 9.1x, and 9.2x. CVSS 10 indicates the flaw is network-exploitable without authentication and grants attackers complete system compromise. The specific attack vector is undisclosed but allows arbitrary code execution.
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= 9.0= 9.10= 9.20CVSS 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 if HP NNMi is installedSearch for HP Network Node Manager i installation directories, services, or processes on the system. Common locations include /opt/HP/NNM or C:\Program Files\HP\NNM. Check running processes for nnm, hpnmm, or related service names.Affected if HP NNMi software is found running or installed on the system
-
Determine installed NNMi versionLocate version information in the NNMi installation directory, typically in a version file, about dialog, or management console. Common file paths include <install_dir>/bin/nnmversion or <install_dir>/version.properties. Run 'nnmversion' command if available in the bin directory.Affected if Installed version matches 9.0.x, 9.1.x, or 9.2.x (including 9.0, 9.10, 9.20 base versions)
-
Check if NNMi management ports are exposedIdentify listening ports associated with NNMi (commonly ports 80, 443, 8080 for web interface). Use netstat or ss to list listening ports and correlate with NNMi processes. Verify if these ports are bound to 0.0.0.0 or accessible from network interfaces.Affected if NNMi management web interface or API ports are listening and accessible from network
-
Verify network accessibility of NNMi interfacesFrom an external host, attempt to reach NNMi management URLs (http://<host>/nnm or similar). Check firewall rules and network ACLs to determine if management interfaces are exposed to untrusted networks or the internet.Affected if NNMi management interface is reachable from untrusted or external networks without VPN or segmentation
The environment is affected if HP NNMi versions 9.0.x, 9.1.x, or 9.2.x are installed and the management interfaces are network-accessible.
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 NNMi; if unavailable, restrict network access to management interfaces and implement compensating controls such as network segmentation and intrusion detection.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2624 — 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-2014-2624 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