# CVE-2017-17423: SQL injection in Quest NetVault Backup

> Remote attackers can execute arbitrary code via SQL injection in Quest NetVault Backup without authentication.

- **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:** 8 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4j3w-3gmf-ff24

## What is CVE-2017-17423?

CVE-2017-17423 is a critical SQL injection vulnerability in Quest NetVault Backup, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Quest NetVault Backup 11.3.0.12. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of NVBUBackupSegment Get method requests. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of the underlying database. Was ZDI-CAN-4234.

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

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

It affects 1 product.


Products: Quest Netvault Backup.

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

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

## Is CVE-2017-17423 being exploited?

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

## Other vulnerabilities in Quest NetVault Backup

- [CVE-2017-17412](https://insights.sbomify.com/CVE-2017-17412/): SQL injection in Quest NetVault Backup (critical 9.8)
- [CVE-2017-17413](https://insights.sbomify.com/CVE-2017-17413/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17414](https://insights.sbomify.com/CVE-2017-17414/): SQL injection in Quest NetVault Backup (critical 9.8)
- [CVE-2017-17415](https://insights.sbomify.com/CVE-2017-17415/): SQL injection in Quest NetVault Backup (critical 9.8)
- [CVE-2017-17416](https://insights.sbomify.com/CVE-2017-17416/): SQL injection in Quest NetVault Backup (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17423 is a critical SQL injection vulnerability in Quest NetVault Backup, published on 8 Feb 2018. 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-17423 in the wild and no public exploit code.

Affected product: Quest NetVault Backup. 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-17423/ (Markdown: https://insights.sbomify.com/CVE-2017-17423/index.md)
```

## Sources

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

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