# CVE-2006-1774: Auth bypass in n/a

> Remote attackers can bypass authentication in HP System Management Homepage when Trust by Certificates is disabled, gaining unauthorized access.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-63p3-x9fp-pjg6

## What is CVE-2006-1774?

CVE-2006-1774 is a high-severity authentication bypass vulnerability in Hp System Management Homepage, published on 13 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HP 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.

## Which versions are affected by CVE-2006-1774?

It affects 2 products.


Products: Hp Compaqhttpserver, Hp System Management Homepage.

## How do I fix CVE-2006-1774?

No fix has been published for CVE-2006-1774 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-1774 being exploited?

There is no known exploitation of CVE-2006-1774 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1774 and fix it if it is affected.

What it is: CVE-2006-1774 is a high-severity authentication bypass vulnerability in Hp System Management Homepage, published on 13 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1774 in the wild and no public exploit code.

Affected product: Hp System Management Homepage. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-1774/ (Markdown: https://insights.sbomify.com/CVE-2006-1774/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-1774
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-1774
- OSV: https://osv.dev/vulnerability/CVE-2006-1774

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-1774/
Summaries are generated and may contain mistakes; the official description above is the record.