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

> Remote attackers can execute arbitrary code via a buffer overflow triggered by a malformed POST request in Flexense VX Search Enterprise.

- **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:** 11 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j2hr-3xh6-w2c7

## What is CVE-2017-15220?

CVE-2017-15220 is a critical memory corruption vulnerability in n/a, published on 11 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Flexense VX Search Enterprise 10.1.12 is vulnerable to a buffer overflow via an empty POST request to a long URI beginning with a /../ substring. This allows remote attackers to execute arbitrary code.

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

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

It affects 1 product.


Products: Flexense Vx Search.

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

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

## Is CVE-2017-15220 being exploited?

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

Public exploit code:

- VX Search Enterprise 10.1.12 - Remote Buffer Overflow (exploitdb)
- VX Search Enterprise v10.1.12 Remote Buffer Overflow (github_poc): https://github.com/vasilerevnic/CVE-2017-15220-vxsearch-rce

## Other vulnerabilities in n/a

- [CVE-2017-15662](https://insights.sbomify.com/CVE-2017-15662/): Denial of service in n/a (high 7.5)
- [CVE-2023-49572](https://insights.sbomify.com/CVE-2023-49572/): XSS vulnerability in VX Search Enterprise (high 7.1)
- [CVE-2023-49573](https://insights.sbomify.com/CVE-2023-49573/): XSS vulnerability in VX Search Enterprise (high 7.1)
- [CVE-2023-49574](https://insights.sbomify.com/CVE-2023-49574/): XSS vulnerability in VX Search Enterprise (high 7.1)
- [CVE-2023-49575](https://insights.sbomify.com/CVE-2023-49575/): XSS vulnerability in VX Search Enterprise (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15220 is a critical memory corruption vulnerability in n/a, published on 11 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-15220 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-15220/ (Markdown: https://insights.sbomify.com/CVE-2017-15220/index.md)
```

## Sources

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

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