CVE-2007-1754 in the critical feed json
PUBCONV.DLL in Microsoft Office Publisher 2007 does not properly clear memory when transferring data from disk to memory, which allows user…
published 2007-07-10 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1748
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.8%
- EPSS 32.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
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".
Exploit prediction
32.78% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
archive.cert.uni-stuttgart.de
/bugtraq/2007/07/msg00254.html
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2007/ms07-037
vendor-advisory
-
vupen.com
/english/advisories/2007/2479
vdb-entry, vendor-advisory
-
secunia.com
/advisories/25988
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1018353
vdb-entry
- research.eeye.com /html/advisories/published/AD20070710.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1871
vdb-entry, signature
-
us-cert.gov
/cas/techalerts/TA07-191A.html
third-party-advisory, us-government-resource
-
osvdb.org
/35953
vdb-entry
-
securityfocus.com
/archive/1/473309/100/0/threaded
mailing-list
Sources
- CVE List CVE-2007-1754
- NVD CVE-2007-1754
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.