CVE-2017-6800
UnknownEPSS 1.72%
Last modified
CVE-2017-6800 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.72% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Ytnef Project | Ytnef | <= 1.9.1 |
| Debian | Debian Linux | 8.0 |
| Debian | Debian Linux | 9.0 |
References
- http://www.debian.org/security/2017/dsa-3846Third Party Advisory
- https://github.com/Yeraze/ytnef/issues/28Exploit, Third Party Advisory
- http://www.debian.org/security/2017/dsa-3846Third Party Advisory
- https://github.com/Yeraze/ytnef/issues/28Exploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-6800?
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.
How severe is CVE-2017-6800?
Severity scoring for CVE-2017-6800 is pending analysis. The EPSS model estimates a 1.72% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6800?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2017-6800?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST