Menu

Star on GitHub · 3.2k

CVE-2017-20012

2.8 · LOW

A vulnerability classified as problematic has been found in WEKA INTEREST Security Scanner up to 1.8.

Published Mar 28, 2022CWE-404EPSS 0.30%

Overview

CVE-2017-20012 is a low-severity vulnerability. It was published on March 28, 2022 and has a CVSS 3.1 base score of 2.8 (LOW).

This vulnerability has a CVSS 3.1 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

A vulnerability classified as problematic has been found in WEKA INTEREST Security Scanner up to 1.8. Affected is Stresstest Scheme Handler which leads to a denial of service. The attack needs to be approached locally. 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-20012?

CVE-2017-20012 is a low-severity vulnerability. It was published on March 28, 2022 and has a CVSS 3.1 base score of 2.8 (LOW).

How severe is CVE-2017-20012?

This vulnerability has a CVSS 3.1 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2017-20012?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-20012?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-20012 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2017

View all