# CVE-2021-29059: ReDOS in IS-SVG

> Attackers can cause denial of service in applications using the IS-SVG library by providing crafted invalid SVG strings that trigger excessive CPU usage.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r8j5-h5cx-65gg, ROOT-APP-NPM-CVE-2021-29059

## What is CVE-2021-29059?

CVE-2021-29059 is a high-severity denial of service vulnerability in n/a, published on 21 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was discovered in IS-SVG version 2.1.0 to 4.2.2 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2021-29059?

2 open source packages ship an affected version, including is-svg. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `is-svg` | npm | From 2.1.0 | 4.3.0 |
| `is-svg` | npm | From 2.1.0 | 4.3.0 |

Products: Is-Svg Project Is-Svg.

## How do I fix CVE-2021-29059?

Upgrade is-svg to 4.3.0 or later.

## Is CVE-2021-29059 being exploited?

There is no known exploitation of CVE-2021-29059 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-28092](https://insights.sbomify.com/CVE-2021-28092/): Regular Expression Denial of Service (ReDoS) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29059 and fix it if it is affected.

What it is: CVE-2021-29059 is a high-severity denial of service vulnerability in n/a, published on 21 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-29059 in the wild and no public exploit code.

Affected packages and fixed versions:
- is-svg (npm): affected from 2.1.0; fixed in 4.3.0
- is-svg (npm): affected from 2.1.0; fixed in 4.3.0

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/CVE-2021-29059/ (Markdown: https://insights.sbomify.com/CVE-2021-29059/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-29059
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-29059
- OSV: https://osv.dev/vulnerability/CVE-2021-29059

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-29059/
Summaries are generated and may contain mistakes; the official description above is the record.