Parsedown before 1.7.2, when safe mode is used and HTML markup is disabled, might allow attackers to execute arbitrary JavaScript code if a script (already running on the affected page) executes the contents of any element with a specific class. This occurs because spaces are permitted in code block infostrings, which interferes with the intended behavior of a single class name beginning with the language- substring.
References
Link | Resource |
---|---|
https://github.com/erusev/parsedown/issues/699 | Exploit Issue Tracking Third Party Advisory |
https://github.com/erusev/parsedown/releases/tag/1.7.2 | Release Notes Third Party Advisory |
https://github.com/erusev/parsedown/issues/699 | Exploit Issue Tracking Third Party Advisory |
https://github.com/erusev/parsedown/releases/tag/1.7.2 | Release Notes Third Party Advisory |
Configurations
History
21 Nov 2024, 04:20
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/erusev/parsedown/issues/699 - Exploit, Issue Tracking, Third Party Advisory | |
References | () https://github.com/erusev/parsedown/releases/tag/1.7.2 - Release Notes, Third Party Advisory |
Information
Published : 2019-04-06 20:29
Updated : 2024-11-21 04:20
NVD link : CVE-2019-10905
Mitre link : CVE-2019-10905
CVE.ORG link : CVE-2019-10905
JSON object : View
Products Affected
parsedown
- parsedown
CWE
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')