GHSA-rm97-x556-q36h CVE-2024-21501
sanitize-html Information Exposure vulnerability
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 1.03%
- Chance of exploitation in the next 30 days. Higher than 63.64% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory
- Fix
2.12.1- Upgrade sanitize-html to this version or later
Description
Versions of the package sanitize-html before 2.12.1 are vulnerable to Information Exposure when used on the backend and with the style attribute allowed, allowing enumeration of files in the system (including project dependencies). An attacker could exploit this vulnerability to gather details about the file system structure and dependencies of the targeted server.
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| sanitize-html | < 2.12.1 |
2.12.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
sanitize-html npm → 2.12.1
- npm
npm install sanitize-html@2.12.1- yarn
yarn add sanitize-html@2.12.1- pnpm
pnpm add sanitize-html@2.12.1
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory
The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.
How to prevent it
- Architecture and Design, Operation, System Configuration: Do not expose file and directory information to the user.
References
Advisories
Packages
Other links
- github.com/apostrophecms/sanitize-html/pull/650
- github.com/apostrophecms/sanitize-html/commit/c5dbdf77fe8b836d3bf4554ea39edb452…
- gist.github.com/Slonser/8b4d061abe6ee1b2e10c7242987674cf
- github.com/apostrophecms/apostrophe/discussions/4436
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4EB5J…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P4I5X…
- security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-6276557
- security.snyk.io/vuln/SNYK-JS-SANITIZEHTML-6256334
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4EB5J…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P4I5X…
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-cv27-6wvh-8x7j ApostropheCMS: Incomplete CVE-2026-53606: `meta http-equiv=refresh` `content` still ships `javascript:` / `data:` URLs | Medium | Also affects sanitize-html |
| GHSA-374f-7chj-9948 ApostropheCMS sanitize-html: SMIL animation namespace-prefix bypass allows javascript: URI injection (XSS) | Low | Also affects sanitize-html |
| GHSA-x3q4-9hxx-gx8m ApostropheCMS sanitize-html: nonTextTags discard region ends early on an implied close, letting <noscript> content render | Medium | Also affects sanitize-html |
| GHSA-c9rx-x947-fp3h ApostropheCMS sanitize-html: unbounded recursion when re-sanitizing the fallback of a discarded iframe (stack overflow, nestingLimit not enforced) | Medium | Also affects sanitize-html |
| GHSA-g8qq-57p8-ggw5 ApostropheCMS: Stored XSS via SVG SMIL URI-list scheme-policy bypass | Medium | Also affects sanitize-html |
| GHSA-jxwj-j7wr-gfrw ApostropheCMS: Mutation-XSS / allowedTags bypass via literal `</textarea/>` solidus close | Medium | Also affects sanitize-html |
| GHSA-vccv-cmxp-4j9h sanitize-html has incomplete URI scheme validation in that allows javascript: URIs through action, formaction, data, poster, and background attributes | Medium | Also affects sanitize-html |
| GHSA-rpr9-rxv7-x643 Apostrophe has default XSS via `xmp` raw-text passthrough in `sanitize-html` | Critical | Also affects sanitize-html |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor