dbcve.org
Whatsup GoldApplication · Progress

CVE-2018-8938

CRITICAL · 9.8 CVSS v3.0 Published 2018-05-01
Fix available
A fix is available. Upgrade to 18.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Code Injection issue was discovered in DlgSelectMibFile.asp in Ipswitch WhatsUp Gold before 2018 (18.0). Malicious actors can inject a specially crafted SNMP MIB file that could allow them to execute arbitrary commands and code on the WhatsUp Gold server.

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 · high confidence

A code injection vulnerability exists in DlgSelectMibFile.asp in Ipswitch WhatsUp Gold before version 18.0. Attackers can upload a specially crafted SNMP MIB file that gets processed by the ASP page in an unsafe manner, allowing arbitrary command and code execution on the underlying server with the privileges of the WhatsUp Gold service account.

MitigationUpgrade to WhatsUp Gold 2018 (18.0) or later which contains the patched version. Until the upgrade can be performed, network-segment the WhatsUp Gold server and restrict access to the vulnerable DlgSelectMibFile.asp endpoint to only trusted management networks.

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
Whatsup GoldApplication
Affected:< 18.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm WhatsUp Gold is installed
    Check the installed programs list in Windows Control Panel or look for the WhatsUp Gold installation directory (typically C:\Program Files\Ipswitch\WhatsUp Gold or similar)
    Affected if WhatsUp Gold is present on the system
  2. Identify the WhatsUp Gold version
    Open the WhatsUp Gold console and check the About section, or look in the installation directory for a version file. Compare the version number to 18.0
    Affected if The installed version is less than 18.0 (for example, 17.x, 16.x, or earlier)
  3. Locate the vulnerable ASP file
    Navigate to the web root directory (typically C:\Program Files\Ipswitch\WhatsUp Gold\HTML\ or similar) and search for the file DlgSelectMibFile.asp
    Affected if The file DlgSelectMibFile.asp exists in the installation
  4. Check if SNMP MIB upload feature is exposed
    Attempt to access the URL https://<yourserver>/DlgSelectMibFile.asp (or check IIS manager for this virtual directory/endpoint)
    Affected if The endpoint is accessible and responds (regardless of authentication status)
  5. Review IIS access logs for the vulnerable endpoint
    Check IIS log files (typically in C:\inetpub\logs\LogFiles) for recent GET or POST requests to DlgSelectMibFile.asp

Your environment is affected if WhatsUp Gold is installed with a version number lower than 18.0 and the DlgSelectMibFile.asp file is present and accessible.

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
Upgrade available Upgrade to 18.0 or later
Fixed in 18.0
Interim mitigation

Upgrade to WhatsUp Gold 2018 (18.0) or later which contains the patched version. Until the upgrade can be performed, network-segment the WhatsUp Gold server and restrict access to the vulnerable DlgSelectMibFile.asp endpoint to only trusted management networks.

Recommended fix Moderate confidence

WhatsUp Gold 18.0 (2018) or later

  1. 1. Backup the current WhatsUp Gold installation, including the database and configuration files
  2. 2. Download WhatsUp Gold version 18.0 or later from the official Ipswitch download portal
  3. 3. Review the official upgrade documentation at docs.ipswitch.com for version 18.0 installation instructions
  4. 4. Stop the WhatsUp Gold services before beginning the upgrade
  5. 5. Install WhatsUp Gold version 18.0 or later following the standard upgrade procedure
  6. 6. Start the WhatsUp Gold services after installation completes
  7. 7. Verify the DlgSelectMibFile.asp component is updated and the vulnerability is resolved
  8. 8. Test that SNMP MIB file imports function correctly in the updated version
Caveat Review Ipswitch compatibility documentation for any changes to plugins, integrations, or API functionality in version 18.0

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

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8938 — 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-2018-8938 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