Skip to content

Cross-site Scripting in remarkable

Moderate severity GitHub Reviewed Published May 29, 2019 to the GitHub Advisory Database • Updated Sep 8, 2023

Package

npm remarkable (npm)

Affected versions

< 1.7.2

Patched versions

1.7.2

Description

In remarkable 1.7.1, lib/parser_inline.js mishandles URL filtering, which allows attackers to trigger XSS via unprintable characters, as demonstrated by a \x0ejavascript: URL.

References

Published by the National Vulnerability Database May 13, 2019
Reviewed May 14, 2019
Published to the GitHub Advisory Database May 29, 2019
Last updated Sep 8, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.087%
(38th percentile)

Weaknesses

CVE ID

CVE-2019-12043

GHSA ID

GHSA-36m4-6v6m-4vpr

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.