Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2016-8005
Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Description
File extension filtering vulnerability in Intel Security McAfee Email Gateway (MEG) before 7.6.404h1128596 allows attackers to fail to identify the file name properly via scanning an email with a forged attached filename that uses a null byte within the filename extension.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Intel Security McAfee Email Gateway 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Intel Security McAfee Email Gateway(MEG)是美国英特尔(Intel)公司(原McAfee公司)公司的一套电子邮件安全解决方案。该方案提供传入威胁防护、传出加密、数据丢失防护等功能。 Intel Security MEG 7.6.404h1128596之前的版本中存在安全漏洞,该漏洞源于程序没有正确的识别文件名称。攻击者可通过扫描邮件利用该漏洞绕过应用程序保护。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
VendorProductAffected VersionsCPESubscribe
IntelMcAfee Email Gateway (MEG) before 7.6.404h1128596 -
II. Public POCs for CVE-2016-8005
#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC
III. Intelligence Information for CVE-2016-8005
Please Login to view more intelligence information
IV. Related Vulnerabilities
V. Comments for CVE-2016-8005

No comments yet


Leave a comment