# CVE-2004-1897: Null dereference in n/a

> Remote attackers can crash Monit by sending a malformed Basic Authentication request, causing a segmentation fault.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1897, GHSA-hjrq-qr8g-2fxf

## What is CVE-2004-1897?

CVE-2004-1897 is a medium-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Administration interface in Monit 1.4 through 4.2 allows remote attackers to cause a denial of service (segmentation fault) by sending a Basic Authentication request without a password, which causes Monit to decrement a null pointer and perform an out-of-bounds read.

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


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

Upgrade to a fixed version.

## Is CVE-2004-1897 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1897 exists.

Public exploit code:

- Monit 4.2 - Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1897 is a medium-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1897 exists.

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-1897/ (Markdown: https://insights.sbomify.com/CVE-2004-1897/index.md)
```

## Sources

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

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