# CVE-2017-11757: Integer overflow in n/a

> Remote attackers can execute arbitrary code via crafted traffic due to an integer underflow causing a heap buffer overflow in the database server.

- **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:** 31 Jul 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2rvr-836w-4qqv

## What is CVE-2017-11757?

CVE-2017-11757 is a critical vulnerability in n/a, published on 31 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in Actian Pervasive PSQL v12.10 and Zen v13 allows remote attackers to execute arbitrary code via crafted traffic to TCP port 1583. The overflow occurs after Server-Client encryption-key exchange. The issue results from an integer underflow that leads to a zero-byte allocation. The _srvLnaConnectMP1 function is affected.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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

It affects 2 products.


Products: Actian Pervasive Psql, Actian Zen.

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

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

## Is CVE-2017-11757 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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