BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2018
CVE-2018-0812High confidence

Microsoft Corporation Equation Editor: Out-of-bounds Write

Microsoft Corporation · Equation Editor

7.8HighCVSS 3.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2018-1618

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Equation Editor in Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allows a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Word Memory Corruption Vulnerability".

What

Equation Editor in Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allows a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Word Memory Corruption Vulnerability".

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Equation Editor in Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allows a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Word Memory Corruption Vulnerability".

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Write → execute code or commands in the affected security context
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
UnauthenticatedRemote code executionCWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Canadian Centre for Cyber Security · English · AV18-005Microsoft security updates

-0748,CVE-2018-0749,CVE-2018-0750,CVE-2018-0751,CVE-2018-0752,CVE-2018-0753,CVE-2018-0754,CVE-2018-0758,CVE-2018-0762,CVE-2018-0764,CVE-2018-0766,CVE-2018-0767,CVE-2018-0768,CVE-2018-0769,CVE-2018-0770,CVE-2018-0772,CVE-2018-0773,CVE-2018-0774,CVE-2018-0775,CVE-2018-0776,CVE-2018-0777,CVE-2018-0778,CVE-2018-0780,CVE-2018-0781,CVE-2018-0784,CVE-2018-0785,CVE-2018-0786,CVE-2018-0788,CVE-2018-0789,CVE-2018-0790,CVE-2018-0791,CVE-2018-0792,CVE-2018-0793,CVE-2018-0794,CVE-2018-0795,CVE-2018-0796,CVE-2018-0797,CVE-2018-0798,CVE-2018-0799,CVE-2018-0800,CVE-2018-0801,CVE-2018-0802,CVE-2018-0803,CVE-2018-0804,CVE-2018-0805,CVE-2018-0806,CVE-2018-0807,CVE-2018-0812,CVE-2018-0818,CVE-2018-0819 Suggested action CCIRC recommends that system administrators test and deploy the vendor-released updates to affected applications accordingly. References https://portal.msrc.microsoft.com/en-us/security-guidance/releasenotedetail/858123b8-25ca-e711-a957-000d3a33cf99 https://portal.msrc.microsoft.com/en-us/security-guidance

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-021Multiples vulnérabilités dans Microsoft Office

De multiples vulnérabilités ont été corrigées dans Microsoft Office . Elles permettent à un attaquant de provoquer une divulgation d'informations, une exécution de code à distance, une injection de code indirecte à distance (XSS) et une usurpation d'identité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2018-001062複数の Microsoft Office 製品の数式エディタにおけるリモートでコードを実行される脆弱性

複数の Microsoft Office 製品の数式エディタには、メモリ内のオブジェクト処理に不備があるため、リモートでコードを実行される脆弱性が存在します。 ベンダは、本脆弱性を「Microsoft Word のメモリ破損の脆弱性」として公開しています。 本脆弱性は、CVE-2018-0797 および CVE-2018-0812 とは異なる脆弱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2018-001044複数の Microsoft Office 製品の数式エディタにおけるリモートでコードを実行される脆弱性

複数の Microsoft Office 製品の数式エディタには、メモリ内のオブジェクト処理に不備があるため、リモートでコードを実行される脆弱性が存在します。 ベンダは、本脆弱性を「Microsoft Word のメモリ破損の脆弱性」として公開しています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Equation Editor: Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Jan 2018 · Last source change 17 Sept 2024, 03:03 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2018-1618
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · patch.
    Before
    no authoritative guidance recorded
    After
    authoritative remediation link · patch
    af854a3a-2127-422b-91ae-364da2661108 ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    af854a3a-2127-422b-91ae-364da2661108 ↗
  4. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  5. CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)
    NIST NVD ↗
  6. ENISA EUVD mappingEUVD-2018-1618 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2018-1618"}
    ENISA EUVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2018-1618↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2018-0812 · cve.blacktree.nl