ghsa-x52f-h5g4-8qv5
Vulnerability from github
Marp Core (@marp-team/marp-core
) from v3.0.2 to v3.9.0 and v4.0.0, are vulnerable to cross-site scripting (XSS) due to improper neutralization of HTML sanitization.
Impact
Marp Core includes an HTML sanitizer with allowlist support. In the affected versions, the built-in allowlist is enabled by default. When the allowlist is active, if insufficient HTML comments are included, the sanitizer may fail to properly sanitize HTML content and lead cross-site scripting (XSS).
Patches
Marp Core v3.9.1 and v4.0.1 have been patched to fix that.
Workarounds
If you are unable to update the package immediately, disable all HTML tags by setting html: false
option in the Marp
class constructor.
javascript
const marp = new Marp({ html: false })
References
- CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- https://github.com/marp-team/marp-core/pull/282
- https://github.com/marp-team/marp-core/commit/61a1def244d1b6faa8e2c0be97ec0b68cab3ab49
Credits
Thanks to @Ry0taK for finding out this vulnerability.
{ "affected": [ { "database_specific": { "last_known_affected_version_range": "\u003c= 3.9.0" }, "package": { "ecosystem": "npm", "name": "@marp-team/marp-core" }, "ranges": [ { "events": [ { "introduced": "3.0.2" }, { "fixed": "3.9.1" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "@marp-team/marp-core" }, "ranges": [ { "events": [ { "introduced": "4.0.0" }, { "fixed": "4.0.1" } ], "type": "ECOSYSTEM" } ], "versions": [ "4.0.0" ] } ], "aliases": [ "CVE-2024-56510" ], "database_specific": { "cwe_ids": [ "CWE-79" ], "github_reviewed": true, "github_reviewed_at": "2024-12-26T18:25:25Z", "nvd_published_at": "2024-12-26T21:15:06Z", "severity": "MODERATE" }, "details": "Marp Core ([`@marp-team/marp-core`](https://www.npmjs.com/package/@marp-team/marp-core)) from v3.0.2 to v3.9.0 and v4.0.0, are vulnerable to cross-site scripting (XSS) due to improper neutralization of HTML sanitization.\n\n### Impact\n\nMarp Core includes an HTML sanitizer with allowlist support. In the affected versions, the built-in allowlist is enabled by default. When the allowlist is active, if insufficient HTML comments are included, the sanitizer may fail to properly sanitize HTML content and lead cross-site scripting (XSS).\n\n### Patches\n\nMarp Core [v3.9.1](https://github.com/marp-team/marp-core/releases/tag/v3.9.1) and [v4.0.1](https://github.com/marp-team/marp-core/releases/tag/v4.0.1) have been patched to fix that.\n\n### Workarounds\n\nIf you are unable to update the package immediately, disable all HTML tags by setting `html: false` option in the `Marp` class constructor.\n\n```javascript\nconst marp = new Marp({ html: false })\n```\n\n### References\n\n- [CWE-79: Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)](https://cwe.mitre.org/data/definitions/79.html)\n- https://github.com/marp-team/marp-core/pull/282\n- https://github.com/marp-team/marp-core/commit/61a1def244d1b6faa8e2c0be97ec0b68cab3ab49\n\n### Credits\n\nThanks to @Ry0taK for finding out this vulnerability.", "id": "GHSA-x52f-h5g4-8qv5", "modified": "2024-12-26T21:45:58Z", "published": "2024-12-26T18:25:25Z", "references": [ { "type": "WEB", "url": "https://github.com/marp-team/marp-core/security/advisories/GHSA-x52f-h5g4-8qv5" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56510" }, { "type": "WEB", "url": "https://github.com/marp-team/marp-core/pull/282" }, { "type": "WEB", "url": "https://github.com/marp-team/marp-core/commit/61a1def244d1b6faa8e2c0be97ec0b68cab3ab49" }, { "type": "PACKAGE", "url": "https://github.com/marp-team/marp-core" }, { "type": "WEB", "url": "https://github.com/marp-team/marp-core/releases/tag/v3.9.1" }, { "type": "WEB", "url": "https://github.com/marp-team/marp-core/releases/tag/v4.0.1" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L", "type": "CVSS_V3" } ], "summary": "Marp Core allows XSS by improper neutralization of HTML sanitization" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.