cve.bz

CVE-2019-3943 mikrotik routeros: Path traversal

8.1 highExploit referenceEPSS 3.7%

High (8.1) in mikrotik routeros. EPSS 3.7% estimated probability of exploitation activity in the next 30 days.

On this page
MikroTik RouterOS versions Stable 6.43.12 and below, Long-term 6.42.12 and below, and Testing 6.44beta75 and below are vulnerable to an authenticated, remote directory traversal via the HTTP or Winbox interfaces. An authenticated, remote attack can use this vulnerability to read and write files outside of the sandbox directory (/rw/disk).

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
3.7% (unchanged from 3.7% a week ago; 3.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 90th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-23 Relative Path Traversal
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2019-3943 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-3943?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-3943?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-3943 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
mikrotik:routerosthrough 6.42.12
mikrotik:routerosthrough 6.43.12
mikrotik:routeros6.41:rc31
mikrotik:routeros6.41:rc32
mikrotik:routeros6.41:rc34
mikrotik:routeros6.41:rc37
mikrotik:routeros6.41:rc38
mikrotik:routeros6.41:rc44
mikrotik:routeros6.41:rc47
mikrotik:routeros6.41:rc50
mikrotik:routeros6.41:rc52
mikrotik:routeros6.41:rc56
mikrotik:routeros6.41:rc61
mikrotik:routeros6.41:rc66
mikrotik:routeros6.42:rc11
mikrotik:routeros6.42:rc12
mikrotik:routeros6.42:rc14
mikrotik:routeros6.42:rc15
mikrotik:routeros6.42:rc18
mikrotik:routeros6.42:rc2
mikrotik:routeros6.42:rc20
mikrotik:routeros6.42:rc23
mikrotik:routeros6.42:rc24
mikrotik:routeros6.42:rc27
mikrotik:routeros6.42:rc28
mikrotik:routeros6.42:rc30
mikrotik:routeros6.42:rc35
mikrotik:routeros6.42:rc37
mikrotik:routeros6.42:rc39
mikrotik:routeros6.42:rc41
mikrotik:routeros6.42:rc43
mikrotik:routeros6.42:rc46
mikrotik:routeros6.42:rc48
mikrotik:routeros6.42:rc49
mikrotik:routeros6.42:rc5
mikrotik:routeros6.42:rc52
mikrotik:routeros6.42:rc56
mikrotik:routeros6.42:rc6
mikrotik:routeros6.42:rc9
mikrotik:routeros6.43:rc11
mikrotik:routeros6.43:rc12
mikrotik:routeros6.43:rc14
mikrotik:routeros6.43:rc17
mikrotik:routeros6.43:rc19
mikrotik:routeros6.43:rc21
mikrotik:routeros6.43:rc23
mikrotik:routeros6.43:rc27
mikrotik:routeros6.43:rc29
mikrotik:routeros6.43:rc3
mikrotik:routeros6.43:rc32
mikrotik:routeros6.43:rc34
mikrotik:routeros6.43:rc4
mikrotik:routeros6.43:rc40
mikrotik:routeros6.43:rc42
mikrotik:routeros6.43:rc44
mikrotik:routeros6.43:rc45
mikrotik:routeros6.43:rc5
mikrotik:routeros6.43:rc51
mikrotik:routeros6.43:rc56
mikrotik:routeros6.43:rc6
mikrotik:routeros6.43:rc64
mikrotik:routeros6.43:rc66
mikrotik:routeros6.43:rc7
mikrotik:routeros6.44:beta14
mikrotik:routeros6.44:beta17
mikrotik:routeros6.44:beta20
mikrotik:routeros6.44:beta28
mikrotik:routeros6.44:beta39
mikrotik:routeros6.44:beta40
mikrotik:routeros6.44:beta50
mikrotik:routeros6.44:beta54
mikrotik:routeros6.44:beta6
mikrotik:routeros6.44:beta61
mikrotik:routeros6.44:beta75
mikrotik:routeros6.44:beta9

Attack patterns (CAPEC)

  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-139 Relative Path Traversal Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON