Microsoft Microsoft Project
5 published vulnerabilities name this product.
As the CNAs write it in their CVE records (vendor and product); the versions are theirs.
| CVE | Vulnerable versions | Title | Severity | Published | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2020-1449 | 2013 Service Pack 1 (32-bit editions) ; 2013 Service Pack 1 (64-bit editions) ; 2016 (32-bit edition) ; … | A remote code execution vulnerability exists in Microsoft Project software when the software fails to check the source markup of a file, aka | HIGH 7.8 | 4.6 % | ||
| CVE-2020-1322 | 2013 Service Pack 1 (32-bit editions) ; 2013 Service Pack 1 (64-bit editions) ; 2016 (32-bit edition) ; … | An information disclosure vulnerability exists when Microsoft Project reads out of bound memory due to an uninitialized variable, aka 'Micro | MEDIUM 6.5 | 5.6 % | ||
| CVE-2020-0760 | 2013 Service Pack 1 (32-bit editions) ; 2013 Service Pack 1 (64-bit editions) ; 2016 (32-bit edition) ; … | A remote code execution vulnerability exists when Microsoft Office improperly loads arbitrary type libraries, aka 'Microsoft Office Remote C | HIGH 8.8 | 8.8 % | ||
| CVE-2019-1264 | 2010 Service Pack 2 (32-bit editions) ; 2010 Service Pack 2 (64-bit editions) ; 2016 (32-bit edition) ; … | A security feature bypass vulnerability exists when Microsoft Office improperly handles input, aka 'Microsoft Office Security Feature Bypass | HIGH 7.8 | 3.8 % | ||
| CVE-2018-8575 | 2010 Service Pack 2 (32-bit editions) ; 2010 Service Pack 2 (64-bit editions) ; 2016 (32-bit edition) ; … | A remote code execution vulnerability exists in Microsoft Project software when it fails to properly handle objects in memory, aka "Microsof | HIGH 7.8 | 20 % |