# CVE-2017-6552: Denial of service in n/a

> An attacker can exhaust the IPv6 routing table to cause a denial of service on Livebox 3 devices, disrupting telephone, Internet, and TV services.

- **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:** 9 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pwhx-m6g7-m6px

## What is CVE-2017-6552?

CVE-2017-6552 is a high-severity denial of service vulnerability in n/a, published on 9 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Livebox 3 Sagemcom SG30_sip-fr-5.15.8.1 devices have an insufficiently large default value for the maximum IPv6 routing table size: it can be filled within minutes. An attacker can exploit this issue to render the affected system unresponsive, resulting in a denial-of-service condition for telephone, Internet, and TV services.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Sagemcom Livebox Firmware.

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

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

## Is CVE-2017-6552 being exploited?

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

Public exploit code:

- Livebox 3 Sagemcom SG30_sip-fr-5.15.8.1 - Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6552 is a high-severity denial of service vulnerability in n/a, published on 9 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-2017-6552 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-6552/ (Markdown: https://insights.sbomify.com/CVE-2017-6552/index.md)
```

## Sources

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

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