dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2011-1849

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
tftpserver.exe in HP Intelligent Management Center (IMC) 5.0 before E0101L02 allows remote attackers to create or overwrite files, and subsequently execute arbitrary code, via a crafted WRQ request.

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

The tftpserver.exe component in HP IMC 5.0 lacks proper validation on WRQ (Write Request) packets, allowing remote attackers to write files to arbitrary locations on the system. By crafting a WRQ request with path traversal sequences or pointing to executable directories, an attacker can drop and subsequently execute malicious code, achieving unauthenticated remote code execution.

MitigationUpgrade HP IMC to version 5.0 E0101L02 or later to obtain the patched tftpserver.exe. If immediate patching is not feasible, disable or block the TFTP service (port 69/UDP) at the network perimeter until the upgrade can be applied.

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. Verify HP IMC installation
    Check if HP Intelligent Management Center is installed on the system by looking for the software in Add/Remove Programs or checking for the IMC installation directory.
    Affected if HP IMC is not installed, this vulnerability does not apply.
  2. Confirm installed version is 5.0
    Locate the HP IMC version information in the software or registry and confirm it is exactly version 5.0.
    Affected if The version is exactly 5.0 - other versions may contain this vulnerability but the provided information indicates this specific version is affected.
  3. Check if tftpserver.exe is running
    Open Task Manager or use command line tools (tasklist /FI "IMAGENAME eq tftpserver.exe") to see if the tftpserver.exe process is active.
    Affected if The tftpserver.exe process is running - this is the vulnerable component.
  4. Verify TFTP service is enabled
    Check the HP IMC service configuration to confirm the TFTP server feature is enabled, or look for the TFTP service in Windows services.
    Affected if The TFTP service is enabled and accessible on the network.
  5. Test UDP port 69 accessibility
    Use a network scanner or the command 'netstat -an | findstr :69' to check if port 69/UDP is listening and potentially reachable from the network.
    Affected if Port 69/UDP is open and reachable - this is the attack vector for sending malicious WRQ packets.

You are affected if HP IMC version 5.0 is installed with the TFTP server component (tftpserver.exe) enabled and port 69/UDP is accessible on your network.

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

Upgrade HP IMC to version 5.0 E0101L02 or later to obtain the patched tftpserver.exe. If immediate patching is not feasible, disable or block the TFTP service (port 69/UDP) at the network perimeter until the upgrade can be applied.

Recommended fix High confidence

HP Intelligent Management Center 5.0 E0101L02

  1. 1. Navigate to the HP support portal and locate the patch for HP Intelligent Management Center 5.0
  2. 2. Download the IMC 5.0 E0101L02 patch or later version
  3. 3. Review the HP patch release notes for any prerequisites or installation requirements
  4. 4. Back up the current IMC configuration and database before applying the patch
  5. 5. Apply the patch following HP's documented installation procedure
  6. 6. Verify that the tftpserver.exe service has been updated and is running correctly
  7. 7. Test that the TFTP server functionality works as expected after the update
  8. 8. Validate that the vulnerability is no longer exploitable
Caveat Review HP release notes for any compatibility or configuration changes required when upgrading to E0101L02

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

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,860
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,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1849 — 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-1849 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