CVE-2017-10140

Public Exploit

Description

Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CONFIG in the current directory.

7.8

CVSS

Severity: High

CVSS 3.0 •

CVSS 2.0 •

EPSS 0.28%

Vendor Advisory redhat.com Vendor Advisory postfix.org

Affected: n/a n/a

References

Link	Tags
http://seclists.org/oss-sec/2017/q3/285	mailing list third party advisory exploit
https://access.redhat.com/errata/RHSA-2019:0366	third party advisory vendor advisory
https://www.oracle.com/security-alerts/cpujul2020.html
http://www.postfix.org/announcements/postfix-3.2.2.html	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-10140?: CVE-2017-10140 has been scored as a high severity vulnerability.
How to fix CVE-2017-10140?: To fix CVE-2017-10140, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-10140 being actively exploited in the wild?: It is possible that CVE-2017-10140 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.