# CVE-2019-10229: Auth bypass in n/a

> Attackers can bypass authentication and log in as existing users when Generic LDAP is configured, leading to account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hmrc-6f76-pj3f

## What is CVE-2019-10229?

CVE-2019-10229 is a high-severity authentication bypass vulnerability in n/a, published on 31 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in MailStore Server (and Service Provider Edition) 9.x through 11.x before 11.2.2. When the directory service (for synchronizing and authenticating users) is set to Generic LDAP, an attacker is able to login as an existing user with an arbitrary password on the second login attempt.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2019-10229?

It affects 2 products.


Products: Mailstore Mailstore, Mailstore Mailstore Server.

## How do I fix CVE-2019-10229?

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

## Is CVE-2019-10229 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10229 and fix it if it is affected.

What it is: CVE-2019-10229 is a high-severity authentication bypass vulnerability in n/a, published on 31 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10229 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-2019-10229/ (Markdown: https://insights.sbomify.com/CVE-2019-10229/index.md)
```

## Sources

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

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