# CVE-2004-1182: Auth bypass in n/a

> Remote attackers can bypass authentication in HylaFAX if a weak hosts.hfaxd configuration is used, allowing unauthorized access to the fax server.

- **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:** Yes
- **Published:** 19 Jan 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1182, DSA-634-1, GHSA-62q2-c83v-qvq3

## What is CVE-2004-1182?

CVE-2004-1182 is a high-severity authentication bypass vulnerability in n/a, published on 19 Jan 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hfaxd in HylaFAX before 4.2.1, when installed with a "weak" hosts.hfaxd file, allows remote attackers to authenticate and bypass intended access restrictions via a crafted (1) username or (2) hostname that satisfies a regular expression that is matched against a hosts.hfaxd entry without a password.

## Which versions are affected by CVE-2004-1182?

It affects 1 product.


Products: Hylafax Hylafax.

## How do I fix CVE-2004-1182?

Upgrade to a fixed version.

## Is CVE-2004-1182 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0886](https://insights.sbomify.com/CVE-2003-0886/): Other in n/a (critical 10.0)
- [CVE-2005-3539](https://insights.sbomify.com/CVE-2005-3539/): Code injection in n/a (high 7.5)
- [CVE-2002-1050](https://insights.sbomify.com/CVE-2002-1050/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0387](https://insights.sbomify.com/CVE-2001-0387/): Memory corruption in n/a (high 7.2)
- [CVE-1999-1340](https://insights.sbomify.com/CVE-1999-1340/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1182 and fix it if it is affected.

What it is: CVE-2004-1182 is a high-severity authentication bypass vulnerability in n/a, published on 19 Jan 2005. 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-2004-1182 in the wild and no public exploit code.

Affected product: n/a. 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-2004-1182/ (Markdown: https://insights.sbomify.com/CVE-2004-1182/index.md)
```

## Sources

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

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