CVE-2019-15506
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 · uneditedAn issue was discovered in Kaseya Virtual System Administrator (VSA) through 9.4.0.37. It has a critical information disclosure vulnerability. An unauthenticated attacker can send properly formatted requests to the web application and download sensitive files and information. For example, the /DATAREPORTS directory can be farmed for reports. Because this directory contains the results of reports such as NMAP, Patch Status, and Active Directory domain metadata, an attacker can easily collect this critical information and parse it for information. There are a number of directories affected.
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 confidenceKaseya VSA through 9.4.0.37 contains an unauthenticated information disclosure vulnerability allowing attackers to directly request and download sensitive files from web-accessible directories such as /DATAREPORTS, which contains NMAP scan results, patch status reports, and Active Directory domain metadata.
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<= 9.4.0.37CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Kaseya VSA installationCheck for Kaseya VSA installation by looking for the service or examining the web server (typically IIS) for Kaseya-specific applications/virtual directories.Affected if Kaseya VSA is installed and running as a web application
-
Determine Kaseya VSA versionAccess the Kaseya VSA login page or admin interface and locate the version information, typically displayed in the footer or in the About/Help section.Affected if The installed version is 9.4.0.37 or any earlier version (9.x, 8.x, etc.)
-
Check web-accessible DATAREPORTS directoryUsing a web browser or curl command, attempt to access http://[VSA_SERVER]/DATAREPORTS/ without providing any authentication credentials.Affected if The directory is accessible and returns an HTTP 200 response listing files or allows file downloads without authentication
-
Verify sensitive file contentsIf the DATAREPORTS directory is accessible, attempt to download known sensitive files such as NMAP scan results, patch status reports, or any files that may contain domain metadata by requesting them directly.Affected if Files containing NMAP scan results, patch status information, or Active Directory metadata can be downloaded without authentication
A system is affected if Kaseya VSA version 9.4.0.37 or earlier is installed and the /DATAREPORTS directory is accessible without authentication, allowing unauthenticated access to sensitive files.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict unauthenticated access to sensitive directories via authentication requirements or access controls; identify and secure all affected directories; apply vendor patch if available.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15506 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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