PatchTheCVEremarkable vulnerabilities and fixes
Recent CVEs affecting remarkable, with upgrade or downgrade steps. 4 tracked.
remarkable has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2019-05-13. Highest priority: CVE-2019-12041 (score 54/100).
- CVE-2019-12043 MEDIUM 6.1 DOWNGRADE In remarkable 1.7.1, lib/parser_inline.js mishandles URL filtering, which allows attackers to trigger XSS via
- CVE-2019-12041 HIGH 7.5 DOWNGRADE lib/common/html_re.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA sect
- CVE-2017-16006 MEDIUM 6.1 UPGRADE Remarkable is a markdown parser
- CVE-2014-10065 MEDIUM 6.1 UPGRADE Certain input when passed into remarkable before 1.4.1 will bypass the bad protocol check that disallows the j
FAQ
How do I fix remarkable vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is remarkable being exploited right now?
None of the tracked remarkable CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which remarkable CVE should I patch first?
CVE-2019-12041 currently ranks highest (54/100): lib/common/html_re.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA sect.