M LinkApplication · Isode

CVE-2022-47634

HIGH · 8.1 CVSS v3.1 Published 2023-01-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
M-Link Archive Server in Isode M-Link R16.2v1 through R17.0 before R17.0v24 allows non-administrative users to access and manipulate archive data via certain HTTP endpoints, aka LINK-2867.

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 · moderate confidence

The M-Link Archive Server in Isode M-Link versions R16.2v1 through R17.0 (prior to R17.0v24) contains an improper access control vulnerability where HTTP endpoints fail to enforce administrative privileges, allowing non-administrative users to access and manipulate archive data they should not be authorized to see or modify.

MitigationUpgrade Isode M-Link to version R17.0v24 or later to remediate this authorization bypass vulnerability.

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
M LinkApplication
Affected:>= r16.2v1, < r17.0v24

CVSS 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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Isode M-Link installation
    Locate the M-Link installation directory or identify the running M-Link process on the system
    Affected if Isode M-Link is found running on the system
  2. Identify installed M-Link version
    Use the product's version lookup mechanism (such as m-link version command, version file in installation directory, or admin console) to determine the exact installed version
    Affected if The installed version is >= R16.2v1 and < R17.0v24
  3. Verify Archive Server module is enabled
    Check M-Link configuration files or admin interface for the Archive Server component status
    Affected if Archive Server module is enabled and configured
  4. Check HTTP endpoint accessibility
    Test HTTP endpoints related to archive functionality using a non-administrative user account to see if unauthorized access is possible
    Affected if Non-administrative users can access or manipulate archive data through HTTP endpoints without proper privilege enforcement
  5. Review user privilege assignments
    Examine the access control configuration to confirm whether administrative privileges are required and enforced for archive operations
    Affected if Administrative privileges are not enforced on archive-related HTTP endpoints

A user is affected if they have Isode M-Link versions R16.2v1 through R17.0 (prior to R17.0v24) installed with the Archive Server module enabled and HTTP endpoints accessible without proper admin privilege validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Isode M-Link to version R17.0v24 or later to remediate this authorization bypass vulnerability.

Recommended fix High confidence

Isode M-Link R17.0v24

  1. Identify the current Isode M-Link version running in the environment
  2. Backup all M-Link configuration files and archive data before proceeding
  3. Stop all M-Link services to prepare for the upgrade
  4. Download Isode M-Link version R17.0v24 or later from the official Isode distribution
  5. Install the upgraded M-Link R17.0v24 package following standard upgrade procedures
  6. Restart M-Link services after the installation completes
  7. Verify the installed version is R17.0v24 or later using system information commands
  8. Log in as a non-administrative user and confirm they can no longer access/archive data via HTTP endpoints to verify the fix
Caveat Review Isode release notes for R17.0v24 to check for any configuration or feature changes from previous versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in M Link Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47634 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47634 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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