What is the severity of CVE-2015-4779?

The severity of CVE-2015-4779 is currently unspecified, but it affects integrity and availability.

How do I fix CVE-2015-4779?

To fix CVE-2015-4779, apply the latest patches provided by Oracle for the affected versions of Berkeley DB.

Which versions of Oracle Berkeley DB are affected by CVE-2015-4779?

CVE-2015-4779 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.

What impact does CVE-2015-4779 have on affected systems?

CVE-2015-4779 may allow local users to affect the integrity and availability of the affected Oracle Berkeley DB systems.

Is CVE-2015-4779 related to other vulnerabilities?

Yes, CVE-2015-4779 is a different vulnerability than CVE-2015-4774 and CVE-2015-4788.

Vulnerability/
CVE-2015-4779

low

3.3

16/7/2015

6/8/2024

CVE-2015-4779

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 integrity and availability via unknown vectors, a different vulnerability than CVE-2015-4774 and CVE-2015-4788.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle Berkeley DB	=11.2.5.1.29
Oracle Berkeley DB	=11.2.5.2.42
Oracle Berkeley DB	=11.2.5.3.28
Oracle Berkeley DB	=12.1.6.0.35

Remedy

http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html

Never miss a vulnerability like this again

Reference Links

http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html

Frequently Asked Questions

What is the severity of CVE-2015-4779?
The severity of CVE-2015-4779 is currently unspecified, but it affects integrity and availability.
How do I fix CVE-2015-4779?
To fix CVE-2015-4779, apply the latest patches provided by Oracle for the affected versions of Berkeley DB.
Which versions of Oracle Berkeley DB are affected by CVE-2015-4779?
CVE-2015-4779 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.
What impact does CVE-2015-4779 have on affected systems?
CVE-2015-4779 may allow local users to affect the integrity and availability of the affected Oracle Berkeley DB systems.
Is CVE-2015-4779 related to other vulnerabilities?
Yes, CVE-2015-4779 is a different vulnerability than CVE-2015-4774 and CVE-2015-4788.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/remedy
agent/author
agent/last-modified-date
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/oracle
canonical/oracle berkeley db
version/oracle berkeley db/11.2.5.1.29
version/oracle berkeley db/11.2.5.2.42
version/oracle berkeley db/11.2.5.3.28
version/oracle berkeley db/12.1.6.0.35

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2015-4779?
The severity of CVE-2015-4779 is currently unspecified, but it affects integrity and availability.
How do I fix CVE-2015-4779?
To fix CVE-2015-4779, apply the latest patches provided by Oracle for the affected versions of Berkeley DB.
Which versions of Oracle Berkeley DB are affected by CVE-2015-4779?
CVE-2015-4779 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.
What impact does CVE-2015-4779 have on affected systems?
CVE-2015-4779 may allow local users to affect the integrity and availability of the affected Oracle Berkeley DB systems.
Is CVE-2015-4779 related to other vulnerabilities?
Yes, CVE-2015-4779 is a different vulnerability than CVE-2015-4774 and CVE-2015-4788.