CVE-2022-47581
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 · uneditedIsode M-Vault 16.0v0 through 17.x before 17.0v24 can crash upon an LDAP v1 bind request.
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 confidenceIsode M-Vault versions 16.0v0 through 17.x before 17.0v24 suffers from a denial-of-service vulnerability where processing a specially crafted LDAP v1 bind request causes the application to crash.
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>= 16.0v0, <= 17.0v3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify installed Isode M-Vault versionRun the product's version command or check the software metadata (such as 'mvault --version', 'vault version', or the installed package details depending on your installation method)Affected if The version is 16.0v0 through 17.0v3 (inclusive) - versions in this range are vulnerable
-
Locate LDAP server configurationLocate the M-Vault LDAP server configuration file (typically in the product's config directory, often named ldap.conf, mvault.conf, or similar depending on your setup)Affected if No configuration file found means LDAP server may not be running, or configuration location differs from expected paths
-
Verify LDAP v1 bind request handlingInspect the LDAP configuration file for settings related to LDAP v1 protocol support or bind request processing (look for parameters like 'allowv1bind', 'protocolversion', 'ldaploglevel', or similar settings that control LDAP v1 behavior)Affected if LDAP v1 bind requests are explicitly allowed, or there is no restriction preventing v1 bind processing - the vulnerability requires v1 bind requests to be processed
You are affected if your installed Isode M-Vault version is between 16.0v0 and 17.0v3 AND your LDAP server configuration permits processing of LDAP v1 bind requests.
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.
dbcve · scopedUpgrade Isode M-Vault to version 17.0v24 or later to address this vulnerability.
M-Vault 17.0v24
- 1. Backup the current M-Vault configuration and data directories.
- 2. Stop the M-Vault service.
- 3. Obtain the M-Vault 17.0v24 release from Isode (contact support or visit www.isode.com).
- 4. Install M-Vault version 17.0v24 following the standard installation procedure.
- 5. Verify the installation by checking the version number.
- 6. Restart the M-Vault service.
- 7. Test LDAP functionality to confirm the service no longer crashes on LDAP v1 bind requests.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47581 — 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-2022-47581 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