# CVE-2017-10897: Denial of service in BBR-4HG

> Attackers can cause Buffalo broadband routers to become unresponsive due to an input validation flaw, requiring a firmware upgrade.

- **Severity:** Medium 4.5 (`CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r464-cmf2-6xc5

## What is CVE-2017-10897?

CVE-2017-10897 is a medium-severity denial of service vulnerability in BUFFALO INC. BBR-4HG, published on 8 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Input validation issue in Buffalo BBR-4HG and and BBR-4MG broadband routers with firmware 1.00 to 1.48 and 2.00 to 2.07 allows an attacker to cause the device to become unresponsive via unspecified vectors.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Buffalo Bbr-4hg Firmware, Buffalo Bbr-4mg Firmware.

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

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

## Is CVE-2017-10897 being exploited?

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

## Other vulnerabilities in BUFFALO INC. BBR-4HG

- [CVE-2017-10896](https://insights.sbomify.com/CVE-2017-10896/): Cross-site scripting in BBR-4HG (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10897 is a medium-severity denial of service vulnerability in BUFFALO INC. BBR-4HG, published on 8 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10897 in the wild and no public exploit code.

Affected product: BUFFALO INC. BBR-4HG. 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-10897/ (Markdown: https://insights.sbomify.com/CVE-2017-10897/index.md)
```

## Sources

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

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