# CVE-2017-3195: Memory corruption in Service Pack 6

> A stack-based buffer overflow in Commvault Edge Communication Service allows attackers to execute arbitrary code with administrative privileges.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 15 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h4f8-5wh7-64hg

## What is CVE-2017-3195?

CVE-2017-3195 is a critical memory corruption vulnerability in Commvault Service Pack 6, published on 15 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Commvault Edge Communication Service (cvd) prior to version 11 SP7 or version 11 SP6 with hotfix 590 is prone to a stack-based buffer overflow vulnerability that could lead to arbitrary code execution with administrative privileges.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Commvault Edge.

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

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

## Is CVE-2017-3195 being exploited?

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

Public exploit code:

- CommVault Edge 11 SP6 - Stack Buffer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3195 is a critical memory corruption vulnerability in Commvault Service Pack 6, published on 15 Dec 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-3195 in the wild and no public exploit code.

Affected product: Commvault Service Pack 6. 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-3195/ (Markdown: https://insights.sbomify.com/CVE-2017-3195/index.md)
```

## Sources

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

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