# CVE-2017-6195: SQL injection in n/a

> Pre-authentication blind SQL injection in Ipswitch MOVEit Transfer allows attackers to read or modify database contents without credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 18 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cx4c-rmcf-w67p

## What is CVE-2017-6195?

CVE-2017-6195 is a critical SQL injection vulnerability in n/a, published on 18 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ipswitch MOVEit Transfer (formerly DMZ) allows pre-authentication blind SQL injection. The fixed versions are MOVEit Transfer 2017 9.0.0.201, MOVEit DMZ 8.3.0.30, and MOVEit DMZ 8.2.0.20.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-6195?

It affects 2 products.


Products: Ipswitch Moveit Dmz, Ipswitch Moveit Transfer 2017.

## How do I fix CVE-2017-6195?

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

## Is CVE-2017-6195 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7675](https://insights.sbomify.com/CVE-2015-7675/): Missing authorization in n/a (medium 6.5)
- [CVE-2015-7676](https://insights.sbomify.com/CVE-2015-7676/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2015-7680](https://insights.sbomify.com/CVE-2015-7680/): Information disclosure in n/a (medium 5.3)
- [CVE-2015-7677](https://insights.sbomify.com/CVE-2015-7677/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6195 and fix it if it is affected.

What it is: CVE-2017-6195 is a critical SQL injection vulnerability in n/a, published on 18 May 2017. 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-2017-6195 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-2017-6195/ (Markdown: https://insights.sbomify.com/CVE-2017-6195/index.md)
```

## Sources

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

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