dbcve.org
MikrotikApplication · Tomtretbar

CVE-2024-38861

HIGH · 7.4 CVSS v3.1 Published 2024-09-27
Fix available
A fix is available. Upgrade to after 2.5.5 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges 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
Improper Certificate Validation in Checkmk Exchange plugin MikroTik allows attackers in MitM position to intercept traffic. This issue affects MikroTik: from 2.0.0 through 2.5.5, from 0.4a_mk through 2.0a.

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 confidence

The Checkmk Exchange plugin for MikroTik fails to properly validate SSL/TLS certificates during connections, allowing an attacker positioned between the plugin and the remote endpoint to intercept and potentially modify encrypted traffic. This is a classic certificate validation bypass where the plugin does not verify the certificate chain, validity dates, or hostname, enabling Man-in-the-Middle attacks.

MitigationUpgrade the MikroTik plugin to version 2.5.6 or later which contains the proper certificate validation fix. Until then, avoid using the plugin across untrusted networks where interception is possible.

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
MikrotikApplication
Affected:<= 2.5.5

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify if the Tomtretbar Mikrotik plugin is installed
    Locate the Checkmk plugin directory and look for files related to the Mikrotik integration (commonly under ~/checkmk/ or /opt/checkmk/ in paths like local/share/checkmk/agents/plugins/ or similar)
    Affected if The plugin files are present on the system
  2. Determine the installed version of the plugin
    Open the plugin file and check for version information in the header, comments, or version variable definitions; compare against the affected range of <= 2.5.5
    Affected if The reported version number is 2.5.5 or lower
  3. Verify the plugin is actively configured or used
    Check Checkmk configuration files or the agent output for configured Mikrotik monitoring targets, or review the plugin registration status in the Checkmk web interface
    Affected if The plugin has Mikrotik host configurations enabled or is executing against MikroTik devices
  4. Confirm SSL/TLS connections are in scope for the plugin
    Review the plugin configuration or script logic to determine if it makes HTTPS or TLS-encrypted connections to MikroTik devices; if the plugin communicates with remote endpoints without certificate validation code, the flaw applies
    Affected if The plugin performs encrypted communication to MikroTik endpoints without proper certificate validation

You are affected if the Tomtretbar Mikrotik plugin is installed with version 2.5.5 or lower and is being used to monitor MikroTik devices over SSL/TLS connections.

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
Upgrade available Upgrade to a release after 2.5.5
Interim mitigation

Upgrade the MikroTik plugin to version 2.5.6 or later which contains the proper certificate validation fix. Until then, avoid using the plugin across untrusted networks where interception is possible.

Recommended fix Moderate confidence

Latest version available on Checkmk Exchange (version > 2.5.5)

  1. 1. Visit the Checkmk Exchange plugin repository at exchange.checkmk.com to find the latest version of the MikroTik plugin.
  2. 2. Download the latest version of the MikroTik plugin (version higher than 2.5.5).
  3. 3. Backup your current Checkmk configuration and the existing MikroTik plugin installation.
  4. 4. Uninstall or remove the vulnerable MikroTik plugin from your Checkmk installation.
  5. 5. Install the new version of the MikroTik plugin by following the installation instructions provided on the Checkmk Exchange site.
  6. 6. Reconfigure the plugin settings as needed, ensuring proper TLS/certificate configuration.
  7. 7. Test the plugin to verify it is functioning correctly and connecting securely to MikroTik devices.
Caveat Review release notes for any configuration changes between your current version and the new version

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

Fix this in Mikrotik Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-38861 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