# CVE-2016-6566: SQL injection in eTRAKiT3

> An unauthenticated remote attacker can inject SQL commands via the login parameter to read or modify backend database data.

- **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:** 13 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3qv8-v62r-xfqv

## What is CVE-2016-6566?

CVE-2016-6566 is a critical SQL injection vulnerability in Sungard eTRAKiT3, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The valueAsString parameter inside the JSON payload contained by the ucLogin_txtLoginId_ClientStat POST parameter of the Sungard eTRAKiT3 software version 3.2.1.17 is not properly validated. An unauthenticated remote attacker may be able to modify the POST request and insert a SQL query which may then be executed by the backend server. eTRAKiT 3.2.1.17 was tested, but other versions may also be vulnerable.

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

## Which versions are affected by CVE-2016-6566?

It affects 1 product.


Products: Sungardas Etrakit3.

## How do I fix CVE-2016-6566?

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

## Is CVE-2016-6566 being exploited?

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

Public exploit code:

- Sungard eTRAKiT3 <= 3.2.1.17 - SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6566 and fix it if it is affected.

What it is: CVE-2016-6566 is a critical SQL injection vulnerability in Sungard eTRAKiT3, published on 13 Jul 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-2016-6566 in the wild and no public exploit code.

Affected product: Sungard eTRAKiT3. 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-2016-6566/ (Markdown: https://insights.sbomify.com/CVE-2016-6566/index.md)
```

## Sources

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

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