Skip to content

← Public intelligence

npm package

remarkable

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratednpmAmendedPublished

    Content Injection in remarkable

    CVE-2014-10065 · GHSA-f9vc-q3hh-qhfv

    Affected
    • npm remarkable < 1.4.1
    Fixed in
    1.4.1· Vendor fix available
    Issue
    Versions 1.4.0 and earlier of remarkable are affected by a cross-site scripting vulnerability. This occurs because vulnerable versions of remarkable did not properly whitelist link protocols, and consequently allowed javascript: to be used. Proof of Concept Markdown Source: Rendered HTML: Recommendation Update to version 1.4.1 or later

    Recommended action: Upgrade to 1.4.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 7.5npmAmendedPublished

    Regular Expression Denial of Service in remarkable

    CVE-2019-12041 · GHSA-q22g-8fr4-qpj4

    Affected
    • npm remarkable < 1.7.2
    Fixed in
    1.7.2· Vendor fix available
    Issue
    lib/common/htmlre.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA section.

    Recommended action: Upgrade to 1.7.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  3. Medium, CVSS 6.1npmAmendedPublished

    Cross-site Scripting in remarkable

    CVE-2019-12043 · GHSA-36m4-6v6m-4vpr

    Affected
    • npm remarkable < 1.7.2
    Fixed in
    1.7.2· Vendor fix available
    Issue
    In remarkable 1.7.1, lib/parserinline.js mishandles URL filtering, which allows attackers to trigger XSS via unprintable characters, as demonstrated by a \x0ejavascript: URL.

    Recommended action: Upgrade to 1.7.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  4. UnratednpmAmendedPublished

    XSS in Data URI in remarkable

    CVE-2017-16006 · GHSA-mrmf-qwxg-7c3h

    Affected
    • npm remarkable <= 1.6.2
    Fixed in
    1.7.0· Vendor fix available
    Issue
    Affected versions of remarkable are vulnerable to cross-site scripting. Vulnerable versions of the package allow the use of data: URIs in links, and can therefore execute javascript. Proof of Concept Recommendation Update to v1.7.0 or later

    Recommended action: Upgrade to 1.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →