CVE-2019-10229
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn MailStore Server 9.x through 11.x before 11.2.2, when configured to use Generic LDAP for user synchronization and authentication, a logic flaw in the login mechanism allows an attacker to authenticate as any existing user with an arbitrary password on the second login attempt, effectively bypassing LDAP authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.6, <= 11.2.1>= 9.6, <= 11.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check MailStore Server versionOpen the MailStore Server administration interface and navigate to the About section, or run 'mailstore-server.exe --version' from the installation directory if CLI access is availableAffected if version falls between 9.6 and 11.2.1 inclusive (compare your installed version to the affected ranges)
-
Verify if Generic LDAP is used for user synchronizationIn the administration interface, go to Users > Synchronization and inspect the synchronization method configuration; look for 'Generic LDAP' as the selected providerAffected if Generic LDAP is selected as the synchronization method
-
Verify if Generic LDAP is used for authenticationIn the administration interface, go to Users > Authentication and inspect the authentication configuration; look for 'Generic LDAP' as the selected providerAffected if Generic LDAP is selected as the authentication method
-
Confirm both synchronization and authentication use Generic LDAPReview both the synchronization and authentication settings together; both must be set to Generic LDAP for this vulnerability to applyAffected if both synchronization AND authentication are configured to use Generic LDAP
You are affected if your MailStore Server version is 9.6 through 11.2.1 AND Generic LDAP is configured for both user synchronization AND authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to MailStore Server 11.2.2 or later to obtain the vendor patch. As a temporary workaround, consider restricting network access to the management interface or implementing additional authentication controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10229 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data