# CVE-2019-17415: Memory corruption in n/a

> Remote unauthenticated attackers can execute arbitrary code via a buffer overflow in the HTTP DELETE method of File Sharing Wizard.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g59r-5x5x-93wp

## What is CVE-2019-17415?

CVE-2019-17415 is a critical memory corruption vulnerability in n/a, published on 9 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Structured Exception Handler (SEH) based buffer overflow in File Sharing Wizard 1.5.0 26-8-2008 allows remote unauthenticated attackers to execute arbitrary code via the HTTP DELETE method, a similar issue to CVE-2019-16724 and CVE-2010-2331.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2019-17415?

It affects 1 product.


Products: Upredsun File Sharing Wizard.

## How do I fix CVE-2019-17415?

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

## Is CVE-2019-17415 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18655](https://insights.sbomify.com/CVE-2019-18655/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-16724](https://insights.sbomify.com/CVE-2019-16724/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-0418](https://insights.sbomify.com/CVE-2024-0418/): iSharer and upRedSun File Sharing Wizard GET Request denial of service (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17415 and fix it if it is affected.

What it is: CVE-2019-17415 is a critical memory corruption vulnerability in n/a, published on 9 Oct 2019. 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-2019-17415 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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