CVE-2017-6800: High severity Ytnef Project Ytnef vulnerability
Published Mar 10, 2017
·Updated
An issue was discovered in ytnef before 1.9.2. An invalid memory access (heap-based buffer over-read) can occur during handling of LONG data types, related to MAPIPrint() in libytnef.
Affected Software
3 affected components
Ytnef Project Ytnef<=1.9.1
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Remediation
Event History
Mar 10, 2017
CVE Published
via MITRE·10:29 AM
Data Sourced
via MITRE·10:29 AM
Description
Data Sourced
via NVD·10:59 AM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-6800?
CVE-2017-6800 has a critical severity level due to the potential for a heap-based buffer over-read.
2
How do I fix CVE-2017-6800?
To fix CVE-2017-6800, upgrade ytnef to version 1.9.2 or later.
3
Which software is affected by CVE-2017-6800?
CVE-2017-6800 affects ytnef versions up to 1.9.1 and Debian Linux versions 8.0 and 9.0.
4
What vulnerability type is associated with CVE-2017-6800?
CVE-2017-6800 is related to a memory corruption vulnerability due to an invalid memory access.
5
Is there a workaround for CVE-2017-6800?
There is no official workaround for CVE-2017-6800; upgrading is the recommended solution.