Skip to content

Defender Daily

Exploited Outlook flaw leaks users’ NTLM hashes through crafted message files

Affected
Office LTSC 2021, Office LTSC 2024 and Microsoft 365 Apps for Enterprise before Microsoft’s Nov 10 updates. All versions and fixes

A flaw in Outlook lets an attacker who gets a user to open a crafted message file collect that user’s NTLMv2 hash. The hash can be used to sign in as them. Microsoft says the flaw has been exploited and fixed it on Nov 10, and CISA added to KEV the same day. The fix is part of Microsoft’s November updates, which Tenable says address 1,093 flaws, 63 of them critical.

Opening the file makes Outlook connect to a network location the attacker controls without showing its usual external-content warning, Microsoft says. That connection discloses the user’s NTLMv2 hash, which the attacker can use to authenticate as the user. The Preview Pane isn’t an attack vector, so the user must open the file. Microsoft rates the flaw Moderate and scores it 6.5 under CVSS 3.1.

The flaw affects Office LTSC 2021, Office LTSC 2024 and Microsoft 365 Apps for Enterprise, Microsoft’s advisory shows. Rapid7 says every supported version of classic Outlook gets a patch. Microsoft hasn’t said who was attacked or how widely, and says the flaw wasn’t publicly disclosed before the fix.

The same release fixes in Windows Search, which Microsoft scores 9.8. An unauthenticated attacker can run code on an Exchange server by emailing a crafted attachment, which Exchange indexes automatically. Rapid7 notes the fix is in Windows, not Exchange, so Exchange servers need the Windows update.

The release also fixes two more critical Windows flaws. in Kerberos, scored 9.8, lets an attacker relay to a domain controller and gain SYSTEM rights. in Schannel, the Windows TLS component, allows code execution from crafted packets, and Microsoft rates it Exploitation More Likely.

LDAP, DNS, DHCP and SQL Server each have a flaw scored 9.8 in the release too. Rapid7 notes that the 23H2 Enterprise, Education and IoT editions of Windows 11 move past their end dates on Nov 11, along with .NET 8 and PowerShell 7.4.

CVE
Vendor
Microsoft

What to do

4 steps

Affected and fixed versions

  • Product
    Office LTSC 2021
    Affected
    Earlier builds
    Fixed
    16.0.14334.21048 or later
  • Product
    Office LTSC 2024
    Affected
    Earlier builds
    Fixed
    16.0.17932.21140 or later
  • Product
    Microsoft 365 Apps for Enterprise
    Affected
    Earlier builds
    Fixed
    The build for each channel on Microsoft’s Office security releases page

Timeline

  1. Nov 10Microsoft fixes the flaw and says it has been exploited, and CISA adds to KEV.

Sources

Subscribe

Get the Daily Brief by email

Weekdays at 7am ET.

We’ll email you a link to confirm. Unsubscribe from any email.