# CVE-2017-13068: SQL injection in QNAP Helpdesk APP

> Remote attackers can perform SQL injection to obtain Helpdesk application information without requiring privileges.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9wh9-2m7m-52vq

## What is CVE-2017-13068?

CVE-2017-13068 is a high-severity SQL injection vulnerability in QNAP Helpdesk APP, published on 6 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QNAP has already patched this vulnerability. This security concern allows a remote attacker to perform an SQL injection on the application and obtain Helpdesk application information. A remote attacker does not require any privileges to successfully execute this attack.

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

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

It affects 1 product.


Products: Qnap Qts Helpdesk.

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

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

## Is CVE-2017-13068 being exploited?

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

Public exploit code:

- QNAP HelpDesk < 1.1.12 - SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-13068 is a high-severity SQL injection vulnerability in QNAP Helpdesk APP, published on 6 Oct 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-13068 in the wild and no public exploit code.

Affected product: QNAP Helpdesk APP. 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-13068/ (Markdown: https://insights.sbomify.com/CVE-2017-13068/index.md)
```

## Sources

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

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