# CVE-2016-7797: Denial of service in n/a

> Remote attackers can cause denial of service by disconnecting nodes via unauthenticated connections when Pacemaker remote is enabled.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-7797, GHSA-gp6f-9wm3-5hr4, RHSA-2016:2578, UBUNTU-CVE-2016-7797

## What is CVE-2016-7797?

CVE-2016-7797 is a high-severity denial of service vulnerability in Opensuse Leap, published on 24 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pacemaker before 1.1.15, when using pacemaker remote, might allow remote attackers to cause a denial of service (node disconnection) via an unauthenticated connection.

Weakness: CWE-254

## Which versions are affected by CVE-2016-7797?

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pacemaker` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-cli` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-cluster-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-cts` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-doc` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-libs-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-nagios-plugins-metadata` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |
| `pacemaker-remote` | Red Hat:enterprise_linux:7::server | All versions | 0:1.1.15-11.el7 |

Products: Clusterlabs Pacemaker, Opensuse Leap, Opensuse Project Leap, Redhat Enterprise Linux High Availability, Redhat Enterprise Linux Resilient Storage, Suse Linux Enterprise High Availability, Suse Linux Enterprise Software Development Kit.

## How do I fix CVE-2016-7797?

Upgrade to a fixed version.

## Is CVE-2016-7797 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2016-7035](https://insights.sbomify.com/CVE-2016-7035/): Missing authorization in pacemaker (high 8.8)
- [CVE-2015-1867](https://insights.sbomify.com/CVE-2015-1867/): Privilege escalation in n/a (high 7.5)
- [CVE-2020-25654](https://insights.sbomify.com/CVE-2020-25654/): Auth bypass in pacemaker (high 7.2)
- [CVE-2011-5271](https://insights.sbomify.com/CVE-2011-5271/): Path traversal in n/a (medium 5.5)
- [CVE-2013-0281](https://insights.sbomify.com/CVE-2013-0281/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7797 and fix it if it is affected.

What it is: CVE-2016-7797 is a high-severity denial of service vulnerability in Opensuse Leap, published on 24 Mar 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-2016-7797 in the wild and no public exploit code.

Affected product: Opensuse Leap. 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-2016-7797/ (Markdown: https://insights.sbomify.com/CVE-2016-7797/index.md)
```

## Sources

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

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