One Article Review

Accueil - L'article:
Source CSO.webp CSO
Identifiant 8291492
Date de publication 2022-12-15 02:00:00 (vue: 2022-12-15 10:05:25)
Titre Microsoft Exchange ProxyNotShell vulnerability explained and how to mitigate it
Texte Last year, two high severity, easily exploitable Microsoft Exchange vulnerabilities dubbed ProxyLogon and ProxyShell made waves in the infosec sphere. Nearly a year later, Exchange Server admins are met with another threat: ProxyNotShell, which in fact is a vulnerability chain comprising two actively exploited flaws: CVE-2022-41040 is a server-side request forgery (SSRF) vulnerability that an authenticated attacker can exploit for privilege escalation. This vulnerability occurs because the root cause of ProxyShell's path confusion flaw remains, as explained further below. CVE-2022-41082 is a deserialization flaw that can be abused to achieve remote code execution (RCE) in Exchange's PowerShell backend once it becomes accessible to the attacker.  Both vulnerabilities impact Microsoft Exchange Server on-premises and hybrid setups running Exchange versions 2013, 2016, and 2019 with an internet-exposed Outlook Web App (OWA) component.To read this article in full, please click here
Envoyé Oui
Condensat 2013 2016 2019 2022 41040 41082 abused accessible achieve actively admins another app are article attacker authenticated backend because becomes below both can cause chain click code component comprising confusion cve deserialization dubbed easily escalation exchange execution explained exploit exploitable exploited exposed fact flaw flaws: forgery full further here high how hybrid impact infosec internet last later made met microsoft mitigate nearly occurs once outlook owa path please powershell premises privilege proxylogon proxynotshell proxyshell rce read remains remote request root running server setups severity side sphere ssrf threat: two versions vulnerabilities vulnerability waves web which year
Tags Vulnerability
Stories
Notes ★★★
Move


L'article ne semble pas avoir été repris aprés sa publication.


L'article ne semble pas avoir été repris sur un précédent.
My email: