# CVE-2017-7219: Memory corruption in n/a

> A remote authenticated attacker can execute arbitrary commands via a heap overflow in Citrix NetScaler Gateway.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j85r-56xq-w6gx

## What is CVE-2017-7219?

CVE-2017-7219 is a high-severity memory corruption vulnerability in n/a, published on 13 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A heap overflow vulnerability in Citrix NetScaler Gateway versions 10.1 before 135.8/135.12, 10.5 before 65.11, 11.0 before 70.12, and 11.1 before 52.13 allows a remote authenticated attacker to run arbitrary commands via unspecified vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Citrix Netscaler Gateway Firmware.

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

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

## Is CVE-2017-7219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18517](https://insights.sbomify.com/CVE-2018-18517/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7219 is a high-severity memory corruption vulnerability in n/a, published on 13 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7219 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-7219/ (Markdown: https://insights.sbomify.com/CVE-2017-7219/index.md)
```

## Sources

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

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