# GHSA-9v62-24cr-58cx: Denial of Service in node-sass


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Sep 2020

## What is GHSA-9v62-24cr-58cx?

GHSA-9v62-24cr-58cx is a vulnerability in node-sass, published on 11 Sep 2020. 

### Official description

Affected versions of `node-sass` are vulnerable to Denial of Service (DoS). Crafted objects passed to the `renderSync` function may trigger C++ assertions in `CustomImporterBridge::get_importer_entry` and `CustomImporterBridge::post_process_return_value` that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service.

## Recommendation

Upgrade to version 4.13.1 or later

## Which versions are affected by GHSA-9v62-24cr-58cx?

2 open source packages ship an affected version, including node-sass.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-sass` | npm | From 3.3.0 | 4.13.1 |
| `node-sass` | npm | From 3.3.0 | 4.13.1 |

## How do I fix GHSA-9v62-24cr-58cx?

Upgrade node-sass to 4.13.1 or later.

## Is GHSA-9v62-24cr-58cx being exploited?

There is no known exploitation of GHSA-9v62-24cr-58cx in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9v62-24cr-58cx and fix it if it is affected.

What it is: GHSA-9v62-24cr-58cx is a vulnerability in node-sass, published on 11 Sep 2020. 
Exploitation: There is no known exploitation of GHSA-9v62-24cr-58cx in the wild and no public exploit code.

Affected packages and fixed versions:
- node-sass (npm): affected from 3.3.0; fixed in 4.13.1
- node-sass (npm): affected from 3.3.0; fixed in 4.13.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-9v62-24cr-58cx/ (Markdown: https://insights.sbomify.com/GHSA-9v62-24cr-58cx/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9v62-24cr-58cx

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9v62-24cr-58cx/
Summaries are generated and may contain mistakes; the official description above is the record.