Show filters
260 Total Results
Displaying 81-90 of 260
Sort by:
Attacker Value
Unknown
CVE-2021-31198
Disclosure Date: May 11, 2021 (last updated February 22, 2025)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-31207
Disclosure Date: May 11, 2021 (last updated February 22, 2025)
Microsoft Exchange Server Security Feature Bypass Vulnerability
0
Attacker Value
Unknown
CVE-2021-28480
Disclosure Date: April 13, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-28481
Disclosure Date: April 13, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-28483
Disclosure Date: April 13, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-26858
Disclosure Date: March 03, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-27078
Disclosure Date: March 03, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-26854
Disclosure Date: March 03, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-26412
Disclosure Date: March 03, 2021 (last updated November 28, 2024)
Microsoft Exchange Server Remote Code Execution Vulnerability
0
Attacker Value
Unknown
CVE-2021-1730
Disclosure Date: February 25, 2021 (last updated November 28, 2024)
<p>A spoofing vulnerability exists in Microsoft Exchange Server which could result in an attack that would allow a malicious actor to impersonate the user.</p>
<p>This update addresses this vulnerability.</p>
<p>To prevent these types of attacks, Microsoft recommends customers to download inline images from different DNSdomains than the rest of OWA. Please see further instructions in the FAQ to put in place this mitigations.</p>
0
