CVE-2011-0269
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 nnmRptConfig.exe in HP OpenView Network Node Manager (OV NNM) 7.51 and 7.53 allows remote attackers to execute arbitrary code via a long schd_select1 parameter.
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 confidenceBuffer overflow vulnerability in HP OpenView Network Node Manager's nnmRptConfig.exe component allows remote attackers to execute arbitrary code by submitting an overly long schd_select1 parameter, indicating insufficient bounds checking on user input.
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= 7.51= 7.53CVSS 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.
-
Verify HP OpenView Network Node Manager is installedLocate the NNM installation directory - typically found under C:\HP\OpenView\NNM or /opt/OV on Unix systems. Check for the presence of the OpenView directory structure and nnmRptConfig.exe binary.Affected if HP OpenView NNM is not installed on the system
-
Identify the installed NNM versionCheck the version of the installed HP OpenView Network Node Manager. On Windows, right-click on the nnmRptConfig.exe executable (usually in \bin\) and view Properties > Version tab. Alternatively, check the HP OpenView installation welcome screen or version.txt in the installation directory.Affected if The installed version is 7.51 or 7.53 (exact match)
-
Confirm nnmRptConfig.exe component is presentVerify that the nnmRptConfig.exe file exists in the NNM installation bin directory. This is the specific component referenced in the CVE as containing the buffer overflow vulnerability.Affected if nnmRptConfig.exe is not found in the installation bin directory
-
Check if the NNM web reporting interface is enabledVerify whether the HP OpenView Network Node Manager web interface (OvWWWNnm) service is running and accessible. This is typically accessed via HTTP/HTTPS on port 80/443 or 8080. Check Windows Services for 'HP OpenView Network Node Manager web interface' or review the web server configuration.Affected if The web reporting interface (OvWWWNnm) is enabled and accessible to the user
-
Determine network exposure of the vulnerable componentReview network accessibility of the NNM web services. Check firewall rules and network ACLs to determine if the nnmRptConfig.exe CGI component is reachable from network segments. The vulnerability is exploitable remotely via HTTP requests containing the schd_select1 parameter.Affected if The NNM web interface is exposed to untrusted network segments or the internet
A system is affected by CVE-2011-0269 if HP OpenView NNM versions 7.51 or 7.53 are installed with the nnmRptConfig.exe web reporting component enabled and accessible on the network.
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 vendor-supplied patches for NNM 7.51/7.53 or upgrade to a patched version; if patches unavailable, consider network segmentation to restrict access to the vulnerable component.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0269 — 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-2011-0269 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