# CVE-2001-1075: Auth bypass in n/a

> Remote attackers can bypass authentication for mail relaying by injecting strings into the maillog file in Cobalt RaQ3 servers.

- **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:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h78v-2wx7-pqf7

## What is CVE-2001-1075?

CVE-2001-1075 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

poprelayd script before 2.0 in Cobalt RaQ3 servers allows remote attackers to bypass authentication for relaying by causing a "POP login by user" string that includes the attacker's IP address to be injected into the maillog log file.

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

It affects 1 product.


Products: Sun Cobalt Raq 3i.

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

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

## Is CVE-2001-1075 being exploited?

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

Public exploit code:

- Cobalt Raq3 PopRelayD - Arbitrary SMTP Relay (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1075 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Mar 2002. 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-2001-1075 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-2001-1075/ (Markdown: https://insights.sbomify.com/CVE-2001-1075/index.md)
```

## Sources

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

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