CVE-2006-1774
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 System Management Homepage (SMH) 2.1.3.132, when running on CompaqHTTPServer/9.9 on Windows, Linux, or Tru64 UNIX, and when "Trust by Certificates" is not enabled, allows remote attackers to bypass authentication via a crafted URL.
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 System Management Homepage 2.1.3.132 running on CompaqHTTPServer/9.9 contains an authentication bypass vulnerability. When 'Trust by Certificates' is not enabled, remote attackers can craft malicious URLs to bypass authentication and gain unauthorized access to the management interface.
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= 9.9= 2.1.3.132CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm HP System Management Homepage is runningCheck for the HP System Management Homepage service or process on the server. On Windows, this typically appears as a service named 'HP System Management Homepage' or 'hp smh'. On Linux, check for process 'hp-smh' or look for the service using 'ps aux | grep smh' or 'systemctl status hp-smh'.Affected if HP System Management Homepage service is not running - the system is not vulnerable to this specific CVE.
-
Identify the HP System Management Homepage versionLocate and inspect the HP SMH version information. On Windows, check the program files directory for HP System Management Homepage or use the Windows registry under HKLM\Software\HP\System Management Homepage\. On Linux, check /opt/hp/hpsmh/ version files or run 'hp-smh -V' if available. Look for version string 2.1.3.132.Affected if The installed version is exactly 2.1.3.132 - this matches the vulnerable version.
-
Identify the CompaqHTTPServer versionCheck the HTTP server version responding to management interface requests. This is typically the CompaqHTTPServer version bundled with HP SMH. You can often retrieve this from HTTP headers by making a request to the management port (usually 2301 or 2381) and examining the Server header, or by checking the server's binary or configuration files.Affected if The HTTP server version is exactly 9.9 - this matches the vulnerable version.
-
Check if Trust by Certificates is enabledExamine the HP SMH configuration for the authentication setting. Look for the 'Trust by Certificates' option in the HP SMH web interface under Security settings, or check the configuration file (typically smhcfg.conf or similar in the HP SMH configuration directory). The setting indicates whether certificate-based authentication is required.Affected if Trust by Certificates is DISABLED or NOT configured - the authentication bypass vulnerability can be exploited. If it is ENABLED, the vulnerability is mitigated.
A system is affected if it runs HP System Management Homepage version 2.1.3.132 with CompaqHTTPServer 9.9 AND has Trust by Certificates disabled, allowing unauthenticated attackers to craft malicious URLs for unauthorized access.
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 dataEnable 'Trust by Certificates' in the HP SMH configuration, or upgrade to a patched version of HP System Management Homepage that addresses this vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1774 — 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-2006-1774 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