dbcve.org
LansweeperApplication

CVE-2015-9264

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-27
Fix available
A fix is available. Upgrade to after 6.0.0.45 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
Lansweeper 4.x through 6.x before 6.0.0.48 allows attackers to execute arbitrary code on the administrator's workstation via a crafted Windows service.

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

Lansweeper versions 4.x through 6.x before 6.0.0.48 contain a vulnerability allowing arbitrary code execution on the administrator's workstation through manipulation of Windows services. The attacker crafts a malicious Windows service which, when processed by the vulnerable Lansweeper instance, executes code with the privileges of the administrator running the Lansweeper service.

MitigationUpgrade Lansweeper to version 6.0.0.48 or later. Review system logs and administrator workstations for indicators of compromise since successful exploitation provides code execution on the admin's machine.

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
LansweeperApplication
Affected:>= 4.0, <= 4.2.0.90>= 5.0, <= 5.3.0.34>= 6.0.0.19, <= 6.0.0.45

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. Check Lansweeper version number
    Open the Lansweeper web console, go to Configuration > Server Settings, or check the version displayed on the login page. Alternatively, locate the Lansweeper installation directory and check the version info in the main executable or configuration files.
    Affected if The installed version is 4.0 through 4.2.0.90, 5.0 through 5.3.0.34, or 6.0.0.19 through 6.0.0.45
  2. Verify Lansweeper service is running
    Open Services.msc and locate the 'Lansweeper Service' or 'Lansweeper' Windows service. Confirm its status is Running.
    Affected if The Lansweeper service is running and the version is within the affected ranges
  3. Confirm Windows service scanning is enabled
    In the Lansweeper web console, navigate to Configuration > Scanning Setup > Scanning Profiles or similar scanning configuration area. Verify that Windows Service scanning or a service-related scanning module is enabled.
    Affected if Windows Service scanning feature is enabled and the Lansweeper version is vulnerable
  4. Review Lansweeper scanning logs for service modifications
    Locate Lansweeper scanning logs in the installation directory or through the web interface. Look for entries related to Windows Service scanning, particularly any unexpected or unauthorized service creation or modification actions.
    Affected if The scanning logs show unauthorized or suspicious Windows service manipulations and the version is affected

You are affected if your Lansweeper version falls within 4.0-4.2.0.90, 5.0-5.3.0.34, or 6.0.0.19-6.0.0.45 and the Windows service scanning feature is enabled.

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 a release after 6.0.0.45
Interim mitigation

Upgrade Lansweeper to version 6.0.0.48 or later. Review system logs and administrator workstations for indicators of compromise since successful exploitation provides code execution on the admin's machine.

Recommended fix High confidence

6.0.0.48 or later (preferably latest 6.x release)

  1. 1. Backup your current Lansweeper database and configuration
  2. 2. Download Lansweeper version 6.0.0.48 or later from the official Lansweeper website (www.lansweeper.com)
  3. 3. Stop the Lansweeper service before upgrading
  4. 4. Run the Lansweeper installer to upgrade to the fixed version
  5. 5. After installation, verify the service starts successfully
  6. 6. Confirm the Lansweeper web console is accessible and functioning properly
  7. 7. Test that asset scanning and other core functions work normally
Caveat Minor: Review release notes for any configuration changes between your current version and 6.0.0.48; test in staging if possible

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

Fix this in Lansweeper 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 the upgrade done

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-2015-9264 — 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-9264 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