# CVE-2004-1891: Information disclosure in n/a

> The FTP daemon fails to log anonymous user actions, potentially hiding malicious activity from administrators on SGI IRIX systems.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4q7c-7fj7-4vmq

## What is CVE-2004-1891?

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

### Official description

The ftp_syslog function in ftpd in SGI IRIX 6.5.20 "doesn't work with anonymous FTP," which has an unknown impact, possibly preventing the actions of anonymous users from being logged.

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

It affects 1 product.


Products: Sgi Irix.

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

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

## Is CVE-2004-1891 being exploited?

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

## Other vulnerabilities in Sgi Irix

- [CVE-2002-1584](https://insights.sbomify.com/CVE-2002-1584/): Privilege escalation in n/a (critical 10.0)
- [CVE-2004-0139](https://insights.sbomify.com/CVE-2004-0139/): Other in n/a (critical 10.0)
- [CVE-2003-0575](https://insights.sbomify.com/CVE-2003-0575/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0473](https://insights.sbomify.com/CVE-2003-0473/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-0359](https://insights.sbomify.com/CVE-2002-0359/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1891 is a medium-severity vulnerability in Sgi Irix, published on 10 May 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-1891 in the wild and no public exploit code.

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

## Sources

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

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