# CVE-2001-1481: Information disclosure in n/a

> Remote attackers can read the world-readable default.aut file to obtain the plaintext administrator password and gain privileged access to the Xitami web server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h5h4-cjwm-9g2f

## What is CVE-2001-1481?

CVE-2001-1481 is a critical vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xitami 2.4 through 2.5 b4 stores the Administrator password in plaintext in the default.aut file, whose default permissions are world-readable, which allows remote attackers to gain privileges.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2001-1481?

It affects 1 product.


Products: Xitami Xitami.

## How do I fix CVE-2001-1481?

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

## Is CVE-2001-1481 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1481 and fix it if it is affected.

What it is: CVE-2001-1481 is a critical vulnerability in n/a, published on 21 Jun 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-2001-1481 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-2001-1481/ (Markdown: https://insights.sbomify.com/CVE-2001-1481/index.md)
```

## Sources

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

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