Skip to content
Fencer Intel
medium 6.5

CVE-2019-1084 json

An information disclosure vulnerability exists when Exchange allows creation of entities with Display Names having non-printable characters.

published 7y ago modified 4mo ago also EUVD-2019-9665

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.3%
EPSS 5.3% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

An information disclosure vulnerability exists when Exchange allows creation of entities with Display Names having non-printable characters. An authenticated attacker could exploit this vulnerability by creating entities with invalid display names, which, when added to conversations, remain invisible. This security update addresses the issue by validating display names upon creation in Microsoft Exchange, and by rendering invalid display names correctly in Microsoft Outlook clients., aka 'Microsoft Exchange Information Disclosure Vulnerability'.

Patch / fix

Is CVE-2019-1084 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

5.33% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

  • Microsoft Microsoft Exchange Server
  • Microsoft Microsoft Outlook
  • Microsoft Microsoft Office
  • Microsoft Microsoft Lync
  • Microsoft Microsoft Lync Basic
  • Microsoft Microsoft Outlook for Android
  • Microsoft Skype for Business
  • Microsoft Skype for Business Basic
  • Microsoft Office 365 ProPlus
  • Microsoft Microsoft Exchange Server 2016
  • Microsoft Microsoft Exchange Server 2019
  • Microsoft Microsoft Exchange Server 2013
  • Microsoft Mail and Calendar
  • Microsoft Outlook for iOS

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.