CVE-2016-4400
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 · uneditedA security vulnerability was identified in HP Network Node Manager i (NNMi) Software 10.00, 10.01 (patch1), 10.01 (patch 2), 10.10. The vulnerability could result in cross-site scripting (XSS).
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 confidenceCross-site scripting (XSS) vulnerability in HP Network Node Manager i (NNMi) versions 10.00, 10.01 through 10.10 allows attackers to inject malicious scripts into web interface pages viewed by other users. The medium severity (5.4) suggests the attack requires some user interaction or specific context to exploit.
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= 10.00= 10.01= 10.10CVSS 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
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 NNMi versionAccess the NNMi web interface and navigate to the About or Help section, or run the command 'oversion' or check the installation directory for version information.Affected if The displayed version matches 10.00, 10.01, 10.02, 10.03, 10.04, 10.05, 10.06, 10.07, 10.08, 10.09, or 10.10.
-
Confirm NNMi web interface is enabledVerify that the NNMi web console is accessible by attempting to reach the NNMi URL (typically https://hostname:8443/nnmi or similar). Check the server status to confirm the web component is running.Affected if The NNMi web interface is active and accessible to users.
-
Review web interface for user input fieldsLog into the NNMi web console and identify pages that accept user-supplied input, such as device names, descriptions, or search fields. Common locations include device inventory, topology views, and search functionality.Affected if User-controllable input fields exist within the web interface without visible output encoding or validation controls.
-
Inspect HTTP responses for unencoded contentUse browser developer tools or a proxy to intercept HTTP responses from NNMi web pages. Submit test input (such as <script>alert(1)</script>) in various fields and observe whether the response reflects the input without encoding.Affected if User input is reflected in responses without proper HTML encoding, indicating potential XSS vulnerability.
A user is affected if NNMi version is 10.00, 10.01, or any version from 10.01 through 10.10 AND the web interface is accessible with unencoded user input fields.
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 the appropriate HP patch or upgrade to a fixed version of NNMi that addresses CVE-2016-4400. Until a patch is available, implement output encoding and input validation on user-supplied data within the NNMi web interface.
- 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-2016-4400 — 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-2016-4400 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