dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2011-1851

HIGH · 10.0 CVSS v2.0 Published 2011-05-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Stack-based buffer overflow in tftpserver.exe in HP Intelligent Management Center (IMC) 5.0 before E0101L02 allows remote attackers to execute arbitrary code via a long mode field.

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 confidence

Stack-based buffer overflow in the tftpserver.exe component of HP Intelligent Management Center (IMC) 5.0. By sending a TFTP request with an excessively long 'mode' field, remote attackers can overflow a stack buffer and achieve arbitrary code execution with the privileges of the TFTP service.

MitigationUpdate HP IMC to version 5.0 E0101L02 or later to obtain the vendor patch. If immediate patching is not feasible, network segmentation and firewall rules should restrict unauthorized access to the TFTP service (UDP port 69).

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
Intelligent Management CenterApplication
Affected:= 5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if HP Intelligent Management Center is installed
    Check for HP IMC installation directories (typically C:\Program Files\HP\IMC or C:\hp\imc) or look in Windows Add/Remove Programs for 'HP Intelligent Management Center'
    Affected if HP IMC 5.0 is installed on the system
  2. Confirm the installed HP IMC version
    Check the version of HP IMC - look at installation properties, version info in Add/Remove Programs, or check version files in the IMC installation directory
    Affected if The installed version is exactly 5.0 (without any E0101L02 or later service pack)
  3. Locate the tftpserver.exe component
    Search for tftpserver.exe in the HP IMC installation directory, typically under the bin or server subfolder
    Affected if tftpserver.exe exists in the HP IMC installation directory
  4. Check if TFTP service is running
    Open Windows Services console (services.msc) and look for the HP IMC TFTP service, or use command 'tasklist /FI "IMAGENAME eq tftpserver.exe"' to check if the process is running
    Affected if tftpserver.exe process is actively running
  5. Verify UDP port 69 is listening
    Run 'netstat -an | findstr :69' or use a port scanner to check if UDP port 69 is in LISTENING state
    Affected if UDP port 69 is open and accepting connections

The system is affected if HP IMC version 5.0 is installed with the tftpserver.exe component running and exposing UDP port 69.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch h20000.www2.hp.com →
Interim mitigation

Update HP IMC to version 5.0 E0101L02 or later to obtain the vendor patch. If immediate patching is not feasible, network segmentation and firewall rules should restrict unauthorized access to the TFTP service (UDP port 69).

Recommended fix High confidence

HP IMC 5.0 E0101L02

  1. Obtain the HP IMC 5.0 E0101L02 patch or hotfix from the official HP support portal using the referenced document URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02822750
  2. Apply the patch to HP Intelligent Management Center 5.0 installations according to HP's installation instructions
  3. Verify the tftpserver.exe component has been updated and the patch is properly installed
  4. Restart the IMC services if required by the patch installation process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1851 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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