dbcve.org
DesktopApplication · Spiceworks

CVE-2015-6021

MEDIUM · 6.1 CVSS v3.0 Published 2017-04-10
Fix available
A fix is available. Upgrade to after 7.5.00093 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Spiceworks Desktop before 2015-12-01 has XSS via an SNMP response.

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

Spiceworks Desktop before December 2015 contains a Cross-Site Scripting (XSS) vulnerability where SNMP responses are not properly sanitized before being rendered in the application interface, allowing injection of arbitrary script content.

MitigationUpdate Spiceworks Desktop to version 2015-12-01 or later to incorporate the patched SNMP response handling. If immediate update is not feasible, consider filtering or validating SNMP responses at the network perimeter.

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
DesktopApplication
Affected:<= 7.5.00093

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Determine Spiceworks Desktop version
    Open the Spiceworks Desktop application, then navigate to Help > About Spiceworks to view the installed version number.
    Affected if The displayed version is 7.5.00093 or earlier.
  2. Confirm SNMP is enabled
    In the Spiceworks web interface, go to Settings > Network Scan or Inventory to verify if any SNMP-enabled devices are being monitored.
    Affected if SNMP monitoring is active and Spiceworks is receiving SNMP responses from devices.
  3. Check SNMP community strings configuration
    Navigate to Settings > Network Scan settings and review the SNMP community strings configured for device discovery.
    Affected if Community strings are configured and SNMP devices are responding to Spiceworks queries.
  4. Verify Spiceworks release date
    Compare the version number and build date from Help > About against December 2015 release timeline.
    Affected if The installed version predates the December 2015 patch release.

A user is affected if their Spiceworks Desktop version is 7.5.00093 or earlier and they have SNMP monitoring enabled, as the XSS vulnerability requires SNMP responses to be processed by the application.

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.

From vendor data
Upgrade available Upgrade to a release after 7.5.00093
Interim mitigation

Update Spiceworks Desktop to version 2015-12-01 or later to incorporate the patched SNMP response handling. If immediate update is not feasible, consider filtering or validating SNMP responses at the network perimeter.

Fix this in Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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