CVE-2011-0890
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 · uneditedHP Discovery & Dependency Mapping Inventory (DDMI) 7.50, 7.51, 7.60, 7.61, 7.70, and 9.30 launches the Windows SNMP service with its default configuration, which allows remote attackers to obtain potentially sensitive information or have unspecified other impact by leveraging the public read community.
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 confidenceHP Discovery & Dependency Mapping Inventory (DDMI) versions 7.50 through 9.30 automatically launches the Windows SNMP service with its default configuration, exposing the public read community string. This allows remote attackers to retrieve potentially sensitive system and network information via SNMP queries.
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.50= 7.51= 7.60= 7.61= 7.70= 9.30CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify HP DDMI installation and versionCheck if HP Discovery & Dependency Mapping Inventory is installed on the system, then determine the installed version by inspecting the program files directory or Add/Remove Programs entry. Compare the version number against the affected range: 7.50, 7.51, 7.60, 7.61, 7.70, or 9.30.Affected if The installed version is any of 7.50, 7.51, 7.60, 7.61, 7.70, or 9.30.
-
Identify running SNMP serviceOpen Windows Services console (services.msc) or run 'sc query snmp' command to check if the SNMP Service is currently running on the system.Affected if The SNMP service (snmp) is running on the system.
-
Inspect SNMP community string configurationOpen the SNMP Service properties in Windows Services console, go to the Security tab, or run 'snmpget' to query the community string. Check the accepted community names configuration.Affected if The community string is set to the default value 'public'.
-
Check SNMP service network accessibilityReview the SNMP service security settings to determine if it accepts SNMP packets from remote hosts. Check the 'Accepted community names' list for hosts that have permission to send SNMP requests.Affected if The SNMP service accepts requests from remote hosts (non-localhost) with the 'public' community string.
The system is affected if HP DDMI version 7.50-9.30 is installed and the SNMP service is running with the default 'public' community string accessible to remote attackers.
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 dataDisable the Windows SNMP service if not required, or change the default 'public' community string to a strong, unique value in the SNMP service configuration.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0890 — 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-0890 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