# CVE-2007-3275: Auth bypass in n/a

> Remote attackers can bypass authentication using blank passwords in LDAP/AD configurations to access arbitrary user accounts and read spam emails.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:C/I:N/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:** 19 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-39wh-r3pj-pmhm

## What is CVE-2007-3275?

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

### Official description

MailWasher Server before 2.2.1, when used with LDAP or Active Directory (AD), does not properly handle blank passwords, which allows remote attackers to access an arbitrary user account and read the spam e-mail messages stored for that account, possibly related to the LoginCheck::doPost function in mwi/servlet/Login.cpp.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-255

## Which versions are affected by CVE-2007-3275?

It affects 1 product.


Products: Mailwasher Mailwasher Server.

## How do I fix CVE-2007-3275?

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

## Is CVE-2007-3275 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3275 and fix it if it is affected.

What it is: CVE-2007-3275 is a high-severity authentication bypass vulnerability in n/a, published on 19 Jun 2007. 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-2007-3275 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-2007-3275/ (Markdown: https://insights.sbomify.com/CVE-2007-3275/index.md)
```

## Sources

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

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