# CVE-2020-28451: Command Injection


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mrxv-pr4h-963q

## What is CVE-2020-28451?

CVE-2020-28451 is a critical vulnerability in image-tiler, published on 2 Aug 2022. 

### Official description

This affects the package image-tiler before 2.0.2.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2020-28451?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `image-tiler` | npm | All versions | None |
| `image-tiler` | npm | All versions | None |

Products: Image-Tiler Project Image-Tiler.

## How do I fix CVE-2020-28451?

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

## Is CVE-2020-28451 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28451 and fix it if it is affected.

What it is: CVE-2020-28451 is a critical vulnerability in image-tiler, published on 2 Aug 2022. 
Exploitation: There is no known exploitation of CVE-2020-28451 in the wild and no public exploit code.

Affected packages and fixed versions:
- image-tiler (npm): affected all versions; no fix listed
- image-tiler (npm): affected all versions; 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-2020-28451/ (Markdown: https://insights.sbomify.com/CVE-2020-28451/index.md)
```

## Sources

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

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