dbcve.org
Interest Security ScannerApplication · Weka

CVE-2017-20011

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in WEKA INTEREST Security Scanner 1.8. It has been rated as problematic. This issue affects some unknown processing of the component HTTP Handler. The manipulation with an unknown input leads to denial of service. It is possible to launch the attack on the local host. 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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A denial of service vulnerability exists in the HTTP Handler component of WEKA INTEREST Security Scanner 1.8. The vulnerability is locally exploitable and allows an attacker to crash the application via manipulated input to the HTTP Handler. The exploit has been publicly disclosed.

MitigationSince the product is no longer supported, migrate to a currently maintained security scanner solution. If continued use is mandatory, restrict local access to the application and implement network-level controls to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Interest Security ScannerApplication
Affected:= 1.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Weka Interest Security Scanner is installed
    Check system for presence of Weka Interest Security Scanner executable or installation directory. Look for program files, common installation paths, or use system inventory tools to enumerate installed security software.
    Affected if The software is found installed on the system
  2. Confirm the installed version is 1.8
    Locate the application executable or version information file (typically via About dialog, version property, or version info in executable metadata). Compare the version number to the affected range.
    Affected if The installed version is exactly 1.8
  3. Verify HTTP Handler component is configured
    Examine application configuration files, registry entries, or service settings to determine if the HTTP Handler module is enabled. Look for HTTP listener configurations, web service settings, or handler mappings within the application.
    Affected if HTTP Handler component is present and enabled in the application configuration
  4. Check for application crash logs or instability
    Review application event logs, crash dumps, or error logs for recent incidents involving the Weka Interest Security Scanner, particularly those mentioning HTTP Handler failures or unexpected termination.
    Affected if Recent crash events or denial of service symptoms related to the HTTP Handler are logged

The system is affected if Weka Interest Security Scanner version 1.8 is installed with the HTTP Handler component enabled, as this specific version and configuration is vulnerable to denial of service via manipulated HTTP input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the product is no longer supported, migrate to a currently maintained security scanner solution. If continued use is mandatory, restrict local access to the application and implement network-level controls to limit exposure.

Recommended fix Moderate confidence
  1. This vulnerability affects WEKA INTEREST Security Scanner 1.8, which is explicitly noted as 'no longer supported by the maintainer' in the official description.
  2. No fixed version, patch, or upgrade path is provided in the available CVE description.
  3. Since the product is end-of-life and unsupported, the recommended remediation is to replace it with an actively maintained alternative security scanner.
  4. If continued use is mandatory, isolate the affected system and restrict local access to minimize exploit impact, though this is not a full remediation.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Interest Security Scanner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-20011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-20011 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data