ytnef vulnerabilities and fixes

Recent CVEs affecting ytnef, with upgrade or downgrade steps. 25 tracked.

ytnef has 25 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 14. Most recent: 2021-05-26. Highest priority: CVE-2017-9058 (score 63/100).

• CVE-2021-3404 HIGH 7.8 DOWNGRADE MITIGATE In ytnef 1.9.3, the SwapWord function in lib/ytnef.c allows remote attackers to cause a denial-of-service (and
• CVE-2021-3403 HIGH 7.8 DOWNGRADE MITIGATE In ytnef 1.9.3, the TNEFSubjectHandler function in lib/ytnef.c allows remote attackers to cause a denial-of-se
• CVE-2017-9474 MEDIUM 5.5 DOWNGRADE In ytnef 1.9.2, the DecompressRTF function in lib/ytnef.c allows remote attackers to cause a denial of service
• CVE-2017-9473 MEDIUM 5.5 DOWNGRADE MITIGATE In ytnef 1.9.2, the TNEFFillMapi function in lib/ytnef.c allows remote attackers to cause a denial of service
• CVE-2017-9472 MEDIUM 5.5 DOWNGRADE In ytnef 1.9.2, the SwapDWord function in lib/ytnef.c allows remote attackers to cause a denial of service (he
• CVE-2017-9471 MEDIUM 5.5 DOWNGRADE MITIGATE In ytnef 1.9.2, the SwapWord function in lib/ytnef.c allows remote attackers to cause a denial of service (hea
• CVE-2017-9470 MEDIUM 5.5 DOWNGRADE In ytnef 1.9.2, the MAPIPrint function in lib/ytnef.c allows remote attackers to cause a denial of service (NU
• CVE-2017-9146 HIGH 8.8 UPGRADE The TNEFFillMapi function in lib/ytnef.c in libytnef in ytnef through 1.9.2 does not ensure a nonzero count va
• CVE-2017-9058 CRITICAL 9.8 UPGRADE MITIGATE In libytnef in ytnef through 1.9.2, there is a heap-based buffer over-read due to incorrect boundary checking
• CVE-2017-6802 HIGH 7.5 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.2
• CVE-2017-6801 HIGH 7.5 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.2
• CVE-2017-6800 HIGH 7.5 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.2
• CVE-2017-6306 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6305 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6304 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6303 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6302 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6301 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6300 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6299 MEDIUM 5.5 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-6298 HIGH 7.8 UPGRADE MITIGATE An issue was discovered in ytnef before 1.9.1
• CVE-2017-12144 MEDIUM 5.5 DOWNGRADE In ytnef 1.9.2, an allocation failure was found in the function TNEFFillMapi in ytnef.c, which allows attacker
• CVE-2017-12142 MEDIUM 5.5 DOWNGRADE In ytnef 1.9.2, an invalid memory read vulnerability was found in the function SwapDWord in ytnef.c, which all
• CVE-2017-12141 MEDIUM 5.5 DOWNGRADE In ytnef 1.9.2, a heap-based buffer overflow vulnerability was found in the function TNEFFillMapi in ytnef.c,
• CVE-2009-3721 HIGH 7.8 MITIGATE MITIGATE Multiple directory traversal and buffer overflow vulnerabilities were discovered in yTNEF, and in Evolution's

FAQ

How do I fix ytnef vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is ytnef being exploited right now?

None of the tracked ytnef CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which ytnef CVE should I patch first?

CVE-2017-9058 currently ranks highest (63/100): In libytnef in ytnef through 1.9.2, there is a heap-based buffer over-read due to incorrect boundary checking .

RSS feed for ytnef · ← Back to latest CVEs