# CVE-2017-20016: WEKA INTEREST Security Scanner Portscan memory allocation

> Remote attackers can cause a denial of service in WEKA INTEREST Security Scanner via excessive memory allocation in the Portscan component.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Mar 2022
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cmfx-9cxf-9xxj

## What is CVE-2017-20016?

CVE-2017-20016 is a medium-severity denial of service vulnerability in WEKA INTEREST Security Scanner, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in WEKA INTEREST Security Scanner up to 1.8 and classified as problematic. This vulnerability affects unknown code of the component Portscan. The manipulation with an unknown input leads to denial of service. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-789 (Memory Allocation with Excessive Size Value)

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

It affects 1 product.


Products: Weka Interest Security Scanner.

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

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

## Is CVE-2017-20016 being exploited?

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

## Other vulnerabilities in WEKA INTEREST Security Scanner

- [CVE-2017-20011](https://insights.sbomify.com/CVE-2017-20011/): WEKA INTEREST Security Scanner HTTP denial of service (low 2.8)
- [CVE-2017-20012](https://insights.sbomify.com/CVE-2017-20012/): WEKA INTEREST Security Scanner Stresstest Scheme denial of service (low 2.8)
- [CVE-2017-20013](https://insights.sbomify.com/CVE-2017-20013/): WEKA INTEREST Security Scanner Stresstest Configuration denial of service (low 2.8)
- [CVE-2017-20014](https://insights.sbomify.com/CVE-2017-20014/): WEKA INTEREST Security Scanner Webspider denial of service (low 2.8)
- [CVE-2017-20015](https://insights.sbomify.com/CVE-2017-20015/): WEKA INTEREST Security Scanner LAN Viewer denial of service (low 2.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20016 is a medium-severity denial of service vulnerability in WEKA INTEREST Security Scanner, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-20016 in the wild and no public exploit code.

Affected product: WEKA INTEREST Security Scanner. 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-20016/ (Markdown: https://insights.sbomify.com/CVE-2017-20016/index.md)
```

## Sources

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

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