# CVE-2021-3189: Open redirect in Slashify

> The slashify Node.js package allows open-redirect attacks via crafted URLs, potentially enabling phishing or malicious redirection.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f4hq-453j-p95f

## What is CVE-2021-3189?

CVE-2021-3189 is a medium-severity vulnerability in n/a, published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The slashify package 1.0.0 for Node.js allows open-redirect attacks, as demonstrated by a localhost:3000///example.com/ substring.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

2 open source packages ship an affected version, including slashify. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `slashify` | npm | All versions to 1.0.0 | None |
| `slashify` | npm | All versions to 1.0.0 | None |

Products: Google Slashify.

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

No fix has been published for CVE-2021-3189 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-3189 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3189 is a medium-severity vulnerability in n/a, published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-3189 in the wild and no public exploit code.

Affected packages and fixed versions:
- slashify (npm): affected all versions up to 1.0.0; no fix listed
- slashify (npm): affected all versions up to 1.0.0; no fix listed

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

## Sources

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

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