CVE-2014-4077 — Microsoft IME Japanese Privilege Escalation Vulnerability

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

• Documented patch — docs.microsoft.com (NIST National Vulnerability Database)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jun 15, 2022 — passed 1583 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Office 2007 Ime, Microsoft Windows 7, Microsoft Windows Server 2003…).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. Apply the fixed version or the patch documented under Remediation.
4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
5. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 54.58%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
• Hunt retroactively in logs from before May 25, 2022 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• Fix documented
  Oct 13, 2026 · NIST National Vulnerability Database
• Affected products added · microsoft/office 2007 ime, microsoft/windows 7, microsoft/windows server 2003, microsoft/windows server 2008, microsoft/
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · Published → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Record published
  Oct 13, 2026
• CVSS changed · 7.8
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Source status changed · → Published
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• 2022
• Added to CISA KEV catalog
  May 24, 2022 · CISA
• 2014
• CVE published
  Nov 11, 2014 · microsoft

Source activity

Repeated readings are counted rather than listed.

• 3× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

7 on the record

• blogs.technet.com/b/srd/archive/2014/11/11/assessing-risk-for-the-november-2014-securit
  x_refsource_CONFIRM, Not Applicable, Vendor Advisory, CVE Program (cve.org) e CISA ADP
• docs.microsoft.com/en-us/security-updates/securitybulletins/2014/ms14-078
  vendor-advisory, x_refsource_MS, Patch, Vendor Advisory, CVE Program (cve.org) e CISA ADP
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• github.com/advisories/GHSA-5rf9-j2cv-922c
  GitHub Security Advisories
• www.securitytracker.com/id/1031197
  vdb-entry, x_refsource_SECTRACK, Broken Link, Third Party Advisory, VDB Entry, CVE Program (cve.org) e CISA ADP
• nvd.nist.gov/vuln/detail/CVE-2014-4077
  GitHub Security Advisories
• www.securitytracker.com/id/1031196
  vdb-entry, x_refsource_SECTRACK, Broken Link, Third Party Advisory, VDB Entry, CVE Program (cve.org) e CISA ADP

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-20940 Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability Jan 13, 2026
• Medium CVE-2026-20936 Windows NDIS Information Disclosure Vulnerability Jan 13, 2026
• High CVE-2026-20931 Windows Telephony Service Elevation of Privilege Vulnerability Jan 13, 2026
• Medium CVE-2026-20927 Windows SMB Server Denial of Service Vulnerability Jan 13, 2026
• Medium CVE-2026-20925 NTLM Hash Disclosure Spoofing Vulnerability Jan 13, 2026
• High CVE-2026-20929 Windows HTTP.sys Elevation of Privilege Vulnerability Jan 13, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No CWE classification.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2014-4077 is "Microsoft IME Japanese Privilege Escalation Vulnerability", rated High. It affects Office 2007 Ime (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 54.58% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.