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

Microsoft Input Method Editor (IME) Japanese vulnerability

Microsoft Input Method Editor (IME) Japanese contains an unspecified privilege escalation vulnerability in IMJPDCT.EXE that allows attackers to bypass sandbox restrictions.

Verdict

Today item — known-exploited.

An unspecified flaw in the Japanese IME component enables sandbox escape and privilege escalation, permitting attackers to execute code with elevated privileges on affected Windows systems.

CISA KEV Yes · 2022-05-253EPSS 0.47679 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 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 2022-05-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.47679 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Input Method Editor (IME) Japanese. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-264 Permissions/Privileges/Access Control — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-264 · Permissions/Privileges/Access ControlAuthorization / access control
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 exploit the unspecified vulnerability in IMJPDCT.EXE to break out of the sandbox environment.
Business
Sandbox isolation controls fail, removing a critical containment layer for untrusted code execution.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I escalate my privileges from the sandbox context to system or administrator level.
Business
Attackers gain elevated access to system resources, enabling lateral movement and persistent compromise.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with elevated privileges on the compromised Windows system.
Business
Full system compromise becomes possible, allowing data theft, malware installation, or further network propagation.
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)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • 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.