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

> Unauthenticated attackers can trigger a buffer overflow in the HTTP server to execute arbitrary code with SYSTEM privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-grh2-3qxf-46m9

## What is CVE-2017-17099?

CVE-2017-17099 is a high-severity memory corruption vulnerability in n/a, published on 3 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There exists an unauthenticated SEH based Buffer Overflow vulnerability in the HTTP server of Flexense SyncBreeze Enterprise v10.1.16. When sending a GET request with an excessive length, it is possible for a malicious user to overwrite the SEH record and execute a payload that would run under the Windows SYSTEM account.

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

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

It affects 1 product.


Products: Flexense Syncbreeze.

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

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

## Is CVE-2017-17099 being exploited?

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

Public exploit code:

- CVE-2020-8012, CVE-2016-10709, CVE-2017-17099, CVE-2017-18047, CVE-2019-1003000, CVE-2018-1999002 (github_poc): https://github.com/wetw0rk/Exploit-Development

## Other vulnerabilities in n/a

- [CVE-2018-6537](https://insights.sbomify.com/CVE-2018-6537/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-14980](https://insights.sbomify.com/CVE-2017-14980/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-17996](https://insights.sbomify.com/CVE-2017-17996/): Memory corruption in n/a (high 8.8)
- [CVE-2020-36946](https://insights.sbomify.com/CVE-2020-36946/): SyncBreeze 10.0.28 - 'login' Denial of Service (high 8.7)
- [CVE-2020-37100](https://insights.sbomify.com/CVE-2020-37100/): Sync Breeze Enterprise 12.4.18 - Unquoted Service Path (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17099 is a high-severity memory corruption vulnerability in n/a, published on 3 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17099 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-17099/ (Markdown: https://insights.sbomify.com/CVE-2017-17099/index.md)
```

## Sources

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

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