CVE-2020-20247
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 · uneditedMikrotik RouterOs before 6.46.5 (stable tree) suffers from a memory corruption vulnerability in the /nova/bin/traceroute process. An authenticated remote attacker can cause a Denial of Service due via the loop counter variable.
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 confidenceMikrotik RouterOS before 6.46.5 contains a memory corruption vulnerability in the /nova/bin/traceroute binary. An authenticated remote attacker can trigger a denial of service by exploiting a loop counter variable that leads to memory corruption.
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.46.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check RouterOS versionRun the command '/system resource print' or '/system identity print' in the RouterOS CLI or Winbox to retrieve the current RouterOS version numberAffected if The displayed version is lower than 6.46.5 (e.g., 6.45.9, 6.44.6, etc.)
-
Verify the traceroute binary existsCheck for the presence of the file /nova/bin/traceroute on the router filesystem using '/file print' or by attempting to access it via the terminalAffected if The /nova/bin/traceroute binary is present on the system
-
Confirm management access is exposedReview accessible management services (www, winbox, ssh, telnet) using '/ip service print' to identify if the router management interface is reachable from untrusted networksAffected if Management services (Winbox, HTTP, SSH, Telnet) are exposed to the internet or untrusted LAN segments where unauthorized users could obtain credentials
-
Identify user accounts with full privilegesRun '/user print' to list all accounts and check for any that have full administrative rights, especially guest or default accounts that could be exploitedAffected if Multiple user accounts exist or weak/default credentials are in use that could allow an attacker to gain authenticated access
The environment is affected if RouterOS version is below 6.46.5 AND the router is accessible to authenticated attackers (management interface exposed to network where attacker can obtain valid credentials).
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.46.5
Upgrade RouterOS to version 6.46.5 or later. If immediate patching is not feasible, limit access to authenticated management interfaces and consider network segmentation to reduce attack surface.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-20247 — 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-2020-20247 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