# CVE-2017-6631: Denial of service in Cisco Yes Set-Top Box

> Unauthenticated remote attackers can cause a denial of service on Cisco Yes set-top boxes by sending malformed XML requests to the HTTP RPC service.

- **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:** No
- **Published:** 7 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-93fp-78rf-wf2r

## What is CVE-2017-6631?

CVE-2017-6631 is a high-severity denial of service vulnerability in Cisco Yes Set-Top Box, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the HTTP remote procedure call (RPC) service of set-top box (STB) receivers manufactured by Cisco for Yes could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability exists because the firmware of an affected device fails to handle certain XML values that are passed to the HTTP RPC service listening on the local subnet of the device. An attacker could exploit this vulnerability by submitting a malformed request to an affected device. A successful attack could cause the affected device to restart, resulting in a DoS condition. Yes has updated the affected devices with firmware that addresses this vulnerability. Customers are not required to take action. Vulnerable Products: This vulnerability affects YesMaxTotal, YesMax HD, and YesQuattro STB devices. Cisco Bug IDs: CSCvd08812.

Weakness: CWE-399

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

It affects 3 products.


Products: Cisco Yesmax Hd Firmware, Cisco Yesmaxtotal Firmware, Cisco Yesquattro Firmware.

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

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

## Is CVE-2017-6631 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6631 is a high-severity denial of service vulnerability in Cisco Yes Set-Top Box, published on 7 Sep 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-6631 in the wild and no public exploit code.

Affected product: Cisco Yes Set-Top Box. 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-6631/ (Markdown: https://insights.sbomify.com/CVE-2017-6631/index.md)
```

## Sources

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

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