CVE-2017-14091

CVE-2017-14091 is a high-severity vulnerability in Trendmicro Scanmail with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Description

A vulnerability in Trend Micro ScanMail for Exchange 12.0 exists in which certain specific installations that utilize a uncommon feature - Other Update Sources - could be exploited to overwrite sensitive files in the ScanMail for Exchange directory.

Frequently asked questions

What is CVE-2017-14091?
A vulnerability in Trend Micro ScanMail for Exchange 12.0 exists in which certain specific installations that utilize a uncommon feature - Other Update Sources - could be exploited to overwrite sensitive files in the ScanMail for Exchange directory.
How severe is CVE-2017-14091?
CVE-2017-14091 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-14091 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-14091?
CVE-2017-14091 affects Trendmicro Scanmail. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-14091?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-14091 published?
CVE-2017-14091 was published on 2017-12-16 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Trendmicro Scanmail

All CVEs affecting Trendmicro Scanmail →

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →