First published: Thu Jul 16 2015(Updated: )
Unspecified vulnerability in the Data Store component in Oracle Berkeley DB 11.2.5.1.29, 11.2.5.2.42, 11.2.5.3.28, and 12.1.6.0.35 allows local users to affect confidentiality, integrity, and availability via unknown vectors, a different vulnerability than CVE-2015-2583, CVE-2015-2624, CVE-2015-2626, CVE-2015-2654, CVE-2015-2656, CVE-2015-4754, CVE-2015-4764, CVE-2015-4775, CVE-2015-4776, CVE-2015-4777, CVE-2015-4778, CVE-2015-4780, CVE-2015-4781, CVE-2015-4782, CVE-2015-4783, CVE-2015-4784, CVE-2015-4785, CVE-2015-4786, CVE-2015-4787, CVE-2015-4789, and CVE-2015-4790.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Berkeley DB | =11.2.5.1.29 | |
Berkeley DB | =11.2.5.2.42 | |
Berkeley DB | =11.2.5.3.28 | |
Berkeley DB | =12.1.6.0.35 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-2640 is classified as a vulnerability that affects confidentiality, integrity, and availability in affected Oracle Berkeley DB versions.
CVE-2015-2640 affects Oracle Berkeley DB versions 11.2.5.1.29, 11.2.5.2.42, 11.2.5.3.28, and 12.1.6.0.35.
To fix CVE-2015-2640, upgrade your Oracle Berkeley DB to a version that is not affected by this vulnerability.
CVE-2015-2640 may allow local users to affect the confidentiality, integrity, and availability of the database.
Yes, CVE-2015-2640 is referenced as a different vulnerability than CVE-2015-2583, CVE-2015-2624, and CVE-2015-2626.