Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2017-20149: Chimay Red

Published Oct 15, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS2.5%85th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendor
Mikrotik
IdentifiersCVE-2017-20149CWE-119

CVE-2017-20149, also known as Chimay Red, is a memory corruption vulnerability in the MikroTik RouterOS web server affecting releases before Stable 6.38.5 and Long-term 6.37.5. The flaw is reachable through the HTTP interface and can be triggered remotely by an unauthenticated attacker via a crafted HTTP request. The available context identifies the issue as memory corruption in the web server but does not provide the specific vulnerable function or code path. Successful exploitation can lead to arbitrary code execution on the affected router. The vulnerability was reportedly exploited in the wild beginning in mid-2017 and later, including by botnet operators.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote, unauthenticated arbitrary code execution on affected MikroTik RouterOS devices. Because the flaw is in the router’s web server, compromise can give an attacker control of the network appliance itself, enabling device takeover, botnet enrollment, traffic manipulation, persistence on the edge device, and use of the router as an initial access foothold. The provided context also notes in-the-wild exploitation and continued scanning activity against internet-facing targets.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict or disable exposure of the RouterOS HTTP management interface, especially from the public internet. Limit administrative access to trusted management networks, enforce network-layer access controls, and place the interface behind VPN or equivalent administrative segmentation. Monitor for exploitation attempts involving crafted HTTP requests to MikroTik web interfaces and for signs of compromise on exposed routers. Because the vulnerability has been exploited in the wild, internet-exposed unpatched systems should be treated as high risk.

Remediation

Patch, then assume compromise.

Upgrade MikroTik RouterOS to a fixed release. The vulnerable versions are releases before Stable 6.38.5 and Long-term 6.37.5, so remediation is to update to Stable 6.38.5 or later, or Long-term 6.37.5 or later, as appropriate for the deployment track. Verify that the HTTP management interface is running the patched version after upgrade.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MikrotikRouterosoperating_system
FAQ

Frequently asked questions

Is CVE-2017-20149 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2017-20149?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2017-20149.
Is there a patch for CVE-2017-20149?
Upgrade MikroTik RouterOS to a fixed release. The vulnerable versions are releases before Stable 6.38.5 and Long-term 6.37.5, so remediation is to update to Stable 6.38.5 or later, or Long-term 6.37.5 or later, as appropriate for the deployment track.
What products are affected by CVE-2017-20149?
Mikrotik Routeros.
How severe is CVE-2017-20149?
CVE-2017-20149 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.5% (85th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.