CVE-2019-15055 json
MikroTik RouterOS through 6.44.5 and 6.45.x through 6.45.3 improperly handles the disk name, which allows authenticated users to delete arb…
published 7y ago modified 4mo ago also EUVD-2019-6141
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
MikroTik RouterOS through 6.44.5 and 6.45.x through 6.45.3 improperly handles the disk name, which allows authenticated users to delete arbitrary files. Attackers can exploit this vulnerability to reset credential storage, which allows them access to the management interface as an administrator without authentication.
Is CVE-2019-15055 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/tenable/routeros/tree/master/poc/cve_2019_15055 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/tenable/routeros/tree/master/poc/cve_2019_15055
exploit, third-party-advisory
-
mikrotik.com
/download/changelogs/testing-release-tree
release-notes, vendor-advisory
-
fortiguard.com
/zeroday/FG-VD-19-108
third-party-advisory
-
medium.com
/tenable-techblog/rooting-routeros-with-a-usb-drive-16d7b8665f90
press/media-coverage, third-party-advisory
- forum.mikrotik.com /viewtopic.php?t=151603
Sources
- CVE List CVE-2019-15055
- NVD CVE-2019-15055
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.