CVE Tools

CVE-2019-1332

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Microsoft SQL Server 2017 Reporting ServicesAffected: unspecifiedUpgrade to: not statedStated by: CVE record
  • Microsoft Power BI Report ServerAffected: unspecifiedUpgrade to: not statedStated by: CVE record
  • Microsoft SQL Server 2019 Reporting ServicesAffected: unspecifiedUpgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your organization runs SQL Server 2017 Reporting Services, SQL Server 2019 Reporting Services, or Power BI Report Server.
  2. If yes, ask your IT team or vendor to confirm the current patch level against Microsoft's security advisory for this issue.
  3. Apply the Microsoft security update for CVE-2019-1332 listed on the Microsoft Security Response Center advisory page.
  4. Warn staff who use SSRS reports not to click suspicious links sent via email or chat until patched.
  5. Confirm patching is complete and no unusual activity occurred in report server logs.

What it is

From the CVE record

A cross-site scripting (XSS) vulnerability exists when Microsoft SQL Server Reporting Services (SSRS) does not properly sanitize a specially-crafted web request to an affected SSRS server, aka 'Microsoft SQL Server Reporting Services XSS Vulnerability'.

In plain language

Written by AI from the record

This is a web bug in Microsoft's SQL Server Reporting Services (and Power BI Report Server) that could let an attacker trick a logged-in user into running malicious code in their browser — it's worth patching soon, but there's no sign it's being actively exploited right now.

Reflected/stored XSS in SSRS (SQL Server 2017/2019 Reporting Services, Power BI Report Server) stems from insufficient sanitization of crafted web requests, allowing script injection in a report viewer session when a victim is lured into clicking a malicious link (CWE-79, PR:N/UI:R).

If you're affected

  • Report viewer session hijacking
  • Admin credential theft via phishing link
  • Unauthorized actions in reporting portal
  • Reputational risk from compromised reports

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

11% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 471 days before any public exploit.

  1. EPSS band changelow → moderateepss band change
  2. OpenVAS check added
  3. Public exploit / PoCsource: github-poc
  4. Patch availablerecord updated
  5. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 6.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory. This one: public exploit.