Insight Management AgentsApplication · Hp

CVE-2010-4112

MEDIUM · 5.0 CVSS v2.0 Published 2010-12-22
Fix available
A fix is available. Upgrade to after 8.5 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
HP Insight Management Agents before 8.6 allows remote attackers to obtain sensitive information via an unspecified request that triggers disclosure of the full path.

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 confidence

HP Insight Management Agents before version 8.6 contains an information disclosure vulnerability that allows remote attackers to obtain the full file system path through unspecified HTTP requests. This path disclosure could aid attackers in reconnaissance for further exploitation.

MitigationUpgrade HP Insight Management Agents to version 8.6 or later to remediate this vulnerability.

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
Insight Management AgentsApplication
Affected:<= 8.5= 6.30.0.0= 6.31.0.0= 6.40.0.0= 7.0.0.0= 7.10.0.0= 7.20.0.0= 7.30.0.0= 7.40.0.0= 7.40.1.0= 7.41.0.0= 7.50.0.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
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 checks

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

  1. Verify HP Insight Management Agents is installed
    Check system for presence of HP Insight Management Agents software. On Windows, check Add/Remove Programs or Program Files for HP SIM or HP Management Agents. On Linux, check for RPM packages using 'rpm -qa | grep -i hp' or 'dpkg -l | grep -i hp'.
    Affected if The software is present on the system
  2. Determine installed version
    Retrieve the version of HP Insight Management Agents. On Windows, check the program's properties in Add/Remove Programs, or look for version info in the HP directory (commonly under C:\Program Files\HP or C:\hp). On Linux, run 'rpm -q hp-smh-templates' or check version files in /opt/hp.
    Affected if Version cannot be determined or is one of the affected versions: <= 8.5, 6.30.0.0, 6.31.0.0, 6.40.0.0, 7.0.0.0, 7.10.0.0, 7.20.0.0, 7.30.0.0, 7.40.0.0, 7.40.1.0, 7.41.0.0, or 7.50.0.0
  3. Confirm HTTP management interface is accessible
    Verify the HP Insight Management Agents HTTP service is running and exposed. Check if port 2301 (HP HTTP service default) or configured HTTP port is listening using 'netstat -an | findstr 2301' on Windows or 'netstat -tuln | grep 2301' on Linux. Confirm the service is accessible from network.
    Affected if The HTTP management interface is exposed and responds to requests
  4. Test for path disclosure
    Send a crafted HTTP request to the HP Management Agents web interface. Using a browser or curl, access the management URL (commonly http://localhost:2301 or the configured HP agent port) and observe if full file system paths are returned in error messages or responses.
    Affected if HTTP responses reveal absolute file system paths

The system is affected if HP Insight Management Agents is installed with a version at or below 8.5 (including the specific listed versions) AND the HTTP management interface is accessible, allowing path disclosure through web requests.

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.

From vendor data
Upgrade available Upgrade to a release after 8.5
Interim mitigation

Upgrade HP Insight Management Agents to version 8.6 or later to remediate this vulnerability.

Fix this in Insight Management Agents Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4112 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-4112 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