First published: Thu Jun 22 2017(Updated: )
It was found that Berkeley DB reads the DB_CONFIG configuration file from the current working directory by default. This happens when calling db_create() with dbenv=NULL; or using the dbm_open() function. References: <a href="http://seclists.org/oss-sec/2017/q2/452">http://seclists.org/oss-sec/2017/q2/452</a> <a href="http://www.postfix.org/announcements/postfix-3.2.2.html">http://www.postfix.org/announcements/postfix-3.2.2.html</a> Proposed patch: <a href="http://seclists.org/oss-sec/2017/q2/475">http://seclists.org/oss-sec/2017/q2/475</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Berkeley DB |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1464032 is classified as moderate risk due to potential exposure to sensitive data.
To fix REDHAT-BUG-1464032, ensure that the DB_CONFIG file is located in a secure directory and consider specifying an absolute path in your application.
REDAHT-BUG-1464032 affects all versions of Oracle Berkeley DB that read the DB_CONFIG from the current working directory.
The impact of REDHAT-BUG-1464032 includes the risk of misconfigured database environments leading to unauthorized access to database configurations.
Yes, REDHAT-BUG-1464032 can potentially lead to data breaches if an attacker is able to access the DB_CONFIG file containing sensitive settings.