CVE-2023-32154
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 RADVD Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Mikrotik RouterOS. Authentication is not required to exploit this vulnerability. The specific flaw exists within the Router Advertisement Daemon. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of root. . Was ZDI-CAN-19797.
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 out-of-bounds write vulnerability exists in the Router Advertisement Daemon (RADVD) component of Mikrotik RouterOS. The flaw results from insufficient validation of user-supplied data during Router Advertisement message processing, allowing an attacker to write past the end of an allocated memory buffer. This memory corruption enables network-adjacent unauthenticated attackers to execute arbitrary code with root privileges.
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.48.7CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/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.
-
Check RouterOS versionRun /system resource print or check the login banner to identify the installed RouterOS versionAffected if The installed version is below 6.48.7 (e.g., 6.48.6, 6.47, 6.46, etc.)
-
Verify IPv6 router advertisement capability is enabledRun /ipv6 nd print or check if IPv6 Neighbor Discovery is configured on interfacesAffected if Router Advertisement (RA) messages are being processed on any interface, indicating RADVD functionality is active
-
Confirm RADVD service statusRun /tool snmp walk .1.3.6.1.4.1.14988.1.1.3 to check RADVD service state, or inspect /ipv6 nd interface configurationAffected if The RADVD service is running and actively sending or processing Router Advertisement messages
-
Check for custom IPv6 prefix configurationsRun /ipv6 nd prefix print to enumerate configured prefixes that trigger RA processingAffected if Any IPv6 prefixes are configured for advertisement, meaning the vulnerable code path is reachable
A system is affected if it runs RouterOS version below 6.48.7 AND has IPv6 Router Advertisement functionality (RADVD) enabled and processing RA messages on network interfaces.
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.48.7
Apply the Mikrotik RouterOS security update that addresses CVE-2023-32154. If immediate patching is not feasible, restrict network adjacency by isolating affected routers from untrusted network segments to reduce attack surface.
RouterOS 6.48.7
- Identify all Mikrotik RouterOS devices running versions prior to 6.48.7
- Backup the current router configuration via the Web interface, WinBox, or SSH (export command)
- Access the router via WinBox, Webfig, or SSH
- Navigate to System > Packages or use the /system package check-for-updates command
- Download and install RouterOS version 6.48.7 or later
- After reboot, verify the upgrade was successful by checking the version with /system resource print
- Confirm the Router Advertisement Daemon (RADVD) service is functioning properly
- Restore configuration if needed from the backup
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32154 — 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-2023-32154 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