CVE-2011-0262
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 the stringToSeconds function in ovutil.dll in ovwebsnmpsrv.exe in HP OpenView Network Node Manager (OV NNM) 7.51 and 7.53 allows remote attackers to execute arbitrary code via large values of variables to jovgraph.exe.
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 in the stringToSeconds function in ovutil.dll within ovwebsnmpsrv.exe in HP OpenView Network Node Manager versions 7.51 and 7.53 allows remote attackers to execute arbitrary code via crafted large values passed to jovgraph.exe.
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.
-
Locate HP OpenView Network Node Manager installationSearch for the OpenView NNM installation directory, typically found in C:\hp\OpenView\Network Node Manager or C:\Program Files\HP\OpenView\Network Node Manager. Check for the presence of the 'ovwebsnmpsrv.exe' and 'jovgraph.exe' executables in the installation folder.Affected if The software is installed and the vulnerable executables (ovwebsnmpsrv.exe, jovgraph.exe) are present on the system.
-
Determine the installed version of OpenView NNMCheck the version of ovwebsnmpsrv.exe or the main NNM installation. Right-click on ovwebsnmpsrv.exe, select Properties, and view the Version tab. Alternatively, check the README or version.info file in the installation directory.Affected if The installed version is 7.51 or 7.53 specifically.
-
Verify presence of vulnerable ovutil.dllLocate ovutil.dll in the installation directory, typically in the bin or system32 subfolder within the OpenView NNM directory. Check the file version by right-clicking the DLL and viewing Properties > Version.Affected if ovutil.dll exists in the NNM installation directory with a version corresponding to NNM 7.51 or 7.53.
-
Check if ovwebsnmpsrv service is runningOpen Windows Services (services.msc) and look for 'HP OpenView Network Node Manager Web Server' or check if ovwebsnmpsrv.exe process is running via Task Manager.Affected if The ovwebsnmpsrv.exe service or process is active, enabling the attack vector through the web interface.
-
Check if jovgraph.exe is accessibleVerify jovgraph.exe exists in the cgi-bin or cgi directory under the OpenView NNM web root (typically in the 'web\/cgi' subdirectory of the installation). This executable handles the stringToSeconds function calls.Affected if jovgraph.exe is present in the cgi-bin directory, making the stringToSeconds buffer overflow exploitable via crafted requests.
A system is affected if HP OpenView Network Node Manager versions 7.51 or 7.53 are installed with the ovwebsnmpsrv web service running and jovgraph.exe accessible, as this configuration enables exploitation of the ovutil.dll buffer overflow.
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 vendor patches for OpenView NNM 7.51/7.53 or upgrade to a patched version to remediate this critical buffer overflow vulnerability.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0262 — 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-0262 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