basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2023-23397
CVE-2023-23397 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Office vulnerability

Microsoft Office Outlook privilege escalation vulnerability enabling NTLM Relay attacks to impersonate users against other services.

Verdict

Today item — known-exploited.

A privilege escalation flaw in Outlook allows attackers to intercept and relay NTLM authentication tokens, gaining unauthorized access to user accounts and connected services without requiring additional credentials.

CISA KEV Yes · 2023-03-143EPSS 0.97408 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
63 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-03-14).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.97408 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Office. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-294 Auth Bypass by Capture-Replay — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious message or calendar invite that triggers Outlook to initiate an NTLM authentication request to an attacker-controlled server.
Business
Users receive seemingly legitimate communications that silently compromise their authentication credentials.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I intercept the NTLM authentication token sent by Outlook and relay it to a legitimate internal service to authenticate as the victim user.
Business
Attackers gain unauthorized access to enterprise systems and data using stolen user credentials without triggering password-based detection.
3

Lateral reach — past segmentation narrative 3

Attacker
I access sensitive resources, modify configurations, or move laterally through the network using the compromised user's privileges.
Business
Confidential data is exposed, systems are compromised, and the attack may spread to critical infrastructure or connected organizations.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 63 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.