ghsa-7chc-jmhv-g4m2
Vulnerability from github
Published
2022-05-01 17:56
Modified
2022-05-01 17:56
Details

PUBCONV.DLL in Microsoft Office Publisher 2007 does not properly clear memory when transferring data from disk to memory, which allows user-assisted remote attackers to execute arbitrary code via a malformed .pub page via a certain negative value, which bypasses a sanitization procedure that initializes critical pointers to NULL, aka the "Publisher Invalid Memory Reference Vulnerability".

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2007-1754",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2007-07-10T22:30:00Z",
      severity: "HIGH",
   },
   details: "PUBCONV.DLL in Microsoft Office Publisher 2007 does not properly clear memory when transferring data from disk to memory, which allows user-assisted remote attackers to execute arbitrary code via a malformed .pub page via a certain negative value, which bypasses a sanitization procedure that initializes critical pointers to NULL, aka the \"Publisher Invalid Memory Reference Vulnerability\".",
   id: "GHSA-7chc-jmhv-g4m2",
   modified: "2022-05-01T17:56:46Z",
   published: "2022-05-01T17:56:46Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2007-1754",
      },
      {
         type: "WEB",
         url: "https://docs.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-037",
      },
      {
         type: "WEB",
         url: "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1871",
      },
      {
         type: "WEB",
         url: "http://archive.cert.uni-stuttgart.de/bugtraq/2007/07/msg00254.html",
      },
      {
         type: "WEB",
         url: "http://osvdb.org/35953",
      },
      {
         type: "WEB",
         url: "http://research.eeye.com/html/advisories/published/AD20070710.html",
      },
      {
         type: "WEB",
         url: "http://secunia.com/advisories/25988",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/archive/1/473309/100/0/threaded",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id?1018353",
      },
      {
         type: "WEB",
         url: "http://www.us-cert.gov/cas/techalerts/TA07-191A.html",
      },
      {
         type: "WEB",
         url: "http://www.vupen.com/english/advisories/2007/2479",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
}


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.