sanitize-html up to 2.12.0 Style Attribute information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in sanitize-html up to 2.12.0. This affects an unknown part of the component Style Attribute Handler. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2024-21501. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in sanitize-html up to 2.12.0. This affects an unknown code of the component Style Attribute Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The weakness was published 02/24/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-21501 since 12/22/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 2.12.1 eliminates this vulnerability. Applying the patch c5dbdf77fe8b836d3bf4554ea39edb45281ec0b4 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (Snyk): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: sanitize-html 2.12.1
Patch: c5dbdf77fe8b836d3bf4554ea39edb45281ec0b4
Timeline
12/22/2023 🔍02/24/2024 🔍
02/24/2024 🔍
04/26/2025 🔍
Sources
Advisory: c5dbdf77fe8b836d3bf4554ea39edb45281ec0b4Status: Confirmed
CVE: CVE-2024-21501 (🔍)
GCVE (CVE): GCVE-0-2024-21501
GCVE (VulDB): GCVE-100-254685
Entry
Created: 02/24/2024 08:08Updated: 04/26/2025 07:18
Changes: 02/24/2024 08:08 (52), 03/14/2024 02:36 (1), 06/11/2024 10:39 (15), 04/26/2025 07:18 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.