CVE-2016-8495

UnknownEPSS 0.90%

Last modified

CVE-2016-8495 is a vulnerability of currently unknown severity. An improper certificate validation vulnerability in Fortinet FortiManager 5.0.6 through 5.2.7 and 5.4.0 through 5.4.1 allows remote attacker to spoof a trusted entity by using a man-in-the-middle (MITM) attack via the Fortisandbox devices probing feature.. EPSS estimates a 0.90% chance of exploitation in the next 30 days.

Description

An improper certificate validation vulnerability in Fortinet FortiManager 5.0.6 through 5.2.7 and 5.4.0 through 5.4.1 allows remote attacker to spoof a trusted entity by using a man-in-the-middle (MITM) attack via the Fortisandbox devices probing feature.

Metrics

EPSS Probability
0.90%

55.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
FortinetFortimanager Firmware5.0.3
FortinetFortimanager Firmware5.0.4
FortinetFortimanager Firmware5.0.5
FortinetFortimanager Firmware5.0.6
FortinetFortimanager Firmware5.0.7
FortinetFortimanager Firmware5.0.8
FortinetFortimanager Firmware5.0.9
FortinetFortimanager Firmware5.0.10
FortinetFortimanager Firmware5.0.11
FortinetFortimanager Firmware5.2.0
FortinetFortimanager Firmware5.2.1
FortinetFortimanager Firmware5.2.2
FortinetFortimanager Firmware5.2.3
FortinetFortimanager Firmware5.2.4
FortinetFortimanager Firmware5.2.6
FortinetFortimanager Firmware5.2.7
FortinetFortimanager Firmware5.4.0
FortinetFortimanager Firmware5.4.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-8495?
An improper certificate validation vulnerability in Fortinet FortiManager 5.0.6 through 5.2.7 and 5.4.0 through 5.4.1 allows remote attacker to spoof a trusted entity by using a man-in-the-middle (MITM) attack via the Fortisandbox devices probing feature.
How severe is CVE-2016-8495?
Severity scoring for CVE-2016-8495 is pending analysis. The EPSS model estimates a 0.90% probability of exploitation in the next 30 days.
How do I fix CVE-2016-8495?
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-2016-8495?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST