CVE-2018-7445
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 · uneditedA buffer overflow was found in the MikroTik RouterOS SMB service when processing NetBIOS session request messages. Remote attackers with access to the service can exploit this vulnerability and gain code execution on the system. The overflow occurs before authentication takes place, so it is possible for an unauthenticated remote attacker to exploit it. All architectures and all devices running RouterOS before versions 6.41.3/6.42rc27 are vulnerable.
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 confidenceA pre-authentication buffer overflow vulnerability exists in the MikroTik RouterOS SMB service when processing NetBIOS session request messages. The overflow occurs in the NetBIOS session handling code before authentication takes place, allowing unauthenticated remote attackers to execute arbitrary code by sending specially crafted SMB NetBIOS session request packets.
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< 6.41.3= 6.42CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify SMB service is enabledOn the MikroTik device, access Winbox or SSH and run: /ip smb print. Alternatively, check via webfig at IP > SMB. Look for the 'enabled' parameter or check if the SMB service is listed as active.Affected if SMB service is enabled and the RouterOS version is in the vulnerable range (< 6.41.3 or = 6.42)
-
Check RouterOS versionRun the command /system resource print in Winbox terminal, SSH, or via API. This displays the installed RouterOS version under the 'version' and 'board' fields.Affected if The version displayed is lower than 6.41.3, or exactly equals 6.42 (for example, 6.40.9, 6.41, 6.41.1, 6.41.2, or 6.42)
-
Confirm SMB is exposed to untrusted networksReview firewall rules at /ip firewall filter print and NAT rules at /ip firewall nat print. Check if the SMB service (TCP port 445) is permitted from WAN or untrusted interface sources.Affected if SMB is accessible from any interface other than trusted LAN segments and the version is vulnerable
If SMB is enabled on a MikroTik device running RouterOS version < 6.41.3 or exactly 6.42, and the service is reachable from untrusted networks, the device is affected by CVE-2018-7445.
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 · scoped6.41.3
Upgrade MikroTik RouterOS to version 6.41.3 or later (or 6.42rc27+ for release candidate track). If immediate upgrade is not feasible, disable or restrict the SMB service (ports 445/139) from untrusted network access using firewall rules.
RouterOS 6.41.3 or later stable release (6.42.x and later are not affected)
- Backup the current RouterOS configuration before upgrading
- Download RouterOS version 6.41.3 or later (such as 6.43.x or 6.44.x stable) from the MikroTik download page
- Access the RouterOS web interface or WinBox, navigate to Files section and upload the new .npk firmware file
- In RouterOS, go to System > RouterBOARD > Packages and click Download & Install, OR use the /system package install command
- Allow the router to reboot and complete the upgrade process
- After reboot, verify the new version is installed using /system resource print or /system routerboard print
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7445 — 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-2018-7445 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