dbcve.org
Sql MonitorApplication · Red Gate

CVE-2020-15526

MEDIUM · 5.9 CVSS v3.1 Published 2020-07-09
Fix available
A fix is available. Upgrade to after 10.1.6 or later.
See remediation →
68/100
Remediation priority · Elevated
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
In Redgate SQL Monitor 7.1.4 through 10.1.6 (inclusive), the scope for disabling some TLS security certificate checks can extend beyond that defined by various options on the Configuration > Notifications pages to disable certificate checking for alert notifications. These TLS security checks are also ignored during monitoring of VMware machines. This would make SQL Monitor vulnerable to potential man-in-the-middle attacks when sending alert notification emails, posting to Slack or posting to webhooks. The vulnerability is fixed in version 10.1.7.

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

Redgate SQL Monitor 7.1.4-10.1.6 contains improper TLS certificate validation where security checks for SSL/TLS certificates are bypassed when sending alert notification emails, posting to Slack, posting to webhooks, and during VMware machine monitoring. This allows man-in-the-middle attackers to intercept sensitive notification data by impersonating legitimate servers.

MitigationUpgrade Redgate SQL Monitor to version 10.1.7 or later to restore proper TLS certificate validation for all notification channels and VMware monitoring.

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
Sql MonitorApplication
Affected:>= 7.1.4, <= 10.1.6

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

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Check if Redgate SQL Monitor is installed
    Look for the SQL Monitor installation directory (typically C:\Program Files\Redgate\SQL Monitor or /var/opt/redgate/sql-monitor on Linux), or check for the SQL Monitor Base Monitor service running on the system.
    Affected if SQL Monitor is not installed.
  2. Determine the installed SQL Monitor version
    Open the SQL Monitor web interface and navigate to the About page (click your username in the top-right and select About), or check the version of the Redgate SQL Monitor Base Monitor service in Windows Services or the version file in the installation directory.
    Affected if Unable to determine the version, or version is not in the range 7.1.4 to 10.1.6.
  3. Check if email alert notifications are configured
    In the SQL Monitor web interface, go to the Alerts menu and select Alert settings. Look for any configured email notification channels under the Notifications section.
    Affected if Email notifications are configured and enabled.
  4. Check if Slack integration is enabled
    In the SQL Monitor web interface, go to the Alerts menu and look for Slack configuration under Notification channels. Verify if any Slack webhook URLs are saved.
    Affected if Slack notifications are configured and enabled.
  5. Check if webhooks are configured
    In the SQL Monitor web interface, go to the Alerts menu and look for Custom webhooks or HTTP headers under Notification channels. Verify if any webhook URLs are saved.
    Affected if Custom webhooks are configured and enabled.
  6. Check if VMware monitoring is enabled
    In the SQL Monitor web interface, go to the Servers or Machines page. Look for any VMware virtual machines being monitored, or check the Add Machine dialog for VMware-related options.
    Affected if VMware machine monitoring is active.

A user is affected if they have SQL Monitor version 7.1.4 through 10.1.6 AND have at least one of the following enabled: email notifications, Slack integration, webhooks, or VMware machine monitoring.

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 10.1.6
Interim mitigation

Upgrade Redgate SQL Monitor to version 10.1.7 or later to restore proper TLS certificate validation for all notification channels and VMware monitoring.

Fix this in Sql Monitor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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