ghsa-x323-9hmm-gv8q
Vulnerability from github
Published
2022-05-13 01:18
Modified
2024-07-25 15:30
Details

Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE is unique from CVE-2018-0797 and CVE-2018-0812.

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2018-0802",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-787",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2018-01-10T01:29:00Z",
      severity: "HIGH",
   },
   details: "Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka \"Microsoft Office Memory Corruption Vulnerability\". This CVE is unique from CVE-2018-0797 and CVE-2018-0812.",
   id: "GHSA-x323-9hmm-gv8q",
   modified: "2024-07-25T15:30:34Z",
   published: "2022-05-13T01:18:29Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2018-0802",
      },
      {
         type: "WEB",
         url: "https://0patch.blogspot.com/2018/01/the-bug-that-killed-equation-editor-how.html",
      },
      {
         type: "WEB",
         url: "https://github.com/rxwx/CVE-2018-0802",
      },
      {
         type: "WEB",
         url: "https://github.com/zldww2011/CVE-2018-0802_POC",
      },
      {
         type: "WEB",
         url: "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0802",
      },
      {
         type: "WEB",
         url: "https://research.checkpoint.com/another-office-equation-rce-vulnerability",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/102347",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1040153",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.