CVE-2019-16160
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 integer underflow in the SMB server of MikroTik RouterOS before 6.45.5 allows remote unauthenticated attackers to crash the service.
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 confidenceAn integer underflow vulnerability exists in the SMB server component of MikroTik RouterOS versions prior to 6.45.5. Remote unauthenticated attackers can exploit this flaw via the network to crash the SMB service, causing a denial of service condition.
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.45.5CVSS 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 the device as MikroTik RouterOSAccess the router via winbox, webfig, or SSH and check the system identity. The router will show as MikroTik device with RouterOS branding.Affected if The device is not a MikroTik RouterOS device
-
Check the RouterOS versionRun '/system resource print' or '/system identity print' in the router's terminal, or view the version in winbox under System > Resources. Compare the version number to 6.45.5.Affected if The installed version is below 6.45.5 (e.g., 6.45.4, 6.44.6, etc.)
-
Verify SMB service is enabledRun '/ip smb print' or check under IP > SMB in winbox/webfig to see if SMB is enabled.Affected if SMB service is enabled and running on the router
-
Check SMB network exposureRun '/ip smb print' to review the 'interface' binding. By default SMB binds to all interfaces. Check under IP > SMB > Interfaces in winbox to see which interfaces SMB is listening on.Affected if SMB is bound to a network-facing interface (such as 'all', 'bridge', or a WAN interface) accessible to remote attackers
A MikroTik RouterOS device is affected if it runs a version prior to 6.45.5 AND has the SMB service enabled and exposed to the network.
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 data6.45.5
Upgrade MikroTik RouterOS to version 6.45.5 or later to resolve the integer underflow vulnerability in the SMB server. If upgrading is not immediately feasible, consider disabling the SMB service if not required.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16160 — 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-16160 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