# CVE-2015-5987: Other in n/a

> Remote attackers can spoof DNS responses by predicting query IDs due to weak randomization in Belkin router firmware.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qqmc-q7xq-xqw8

## What is CVE-2015-5987?

CVE-2015-5987 is a high-severity vulnerability in n/a, published on 31 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Belkin F9K1102 2 devices with firmware 2.10.17 use an improper algorithm for selecting the ID value in the header of a DNS query, which makes it easier for remote attackers to spoof responses by predicting this value.

## Which versions are affected by CVE-2015-5987?

It affects 1 product.


Products: Zyxel Gs1900-10hp Firmware.

## How do I fix CVE-2015-5987?

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

## Is CVE-2015-5987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-7273](https://insights.sbomify.com/CVE-2026-7273/): Zyxel GS1900 Series Switches Stack-Based Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2019-15800](https://insights.sbomify.com/CVE-2019-15800/): Command injection in n/a (critical 9.8)
- [CVE-2015-5988](https://insights.sbomify.com/CVE-2015-5988/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2015-5989](https://insights.sbomify.com/CVE-2015-5989/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-15803](https://insights.sbomify.com/CVE-2019-15803/): Auth bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5987 and fix it if it is affected.

What it is: CVE-2015-5987 is a high-severity vulnerability in n/a, published on 31 Dec 2015. 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-2015-5987 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-2015-5987/ (Markdown: https://insights.sbomify.com/CVE-2015-5987/index.md)
```

## Sources

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

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