What is the severity of CVE-2016-0690?

CVE-2016-0690 is classified with an unspecified severity level affecting the integrity of Oracle Database Server.

How do I fix CVE-2016-0690?

To fix CVE-2016-0690, apply the latest patches provided by Oracle for affected database versions.

Which versions of Oracle Database are affected by CVE-2016-0690?

CVE-2016-0690 affects Oracle Database versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.

Is CVE-2016-0690 a different vulnerability from CVE-2016-0691?

Yes, CVE-2016-0690 is considered a different vulnerability than CVE-2016-0691.

Can local users exploit CVE-2016-0690?

Yes, local users can exploit CVE-2016-0690 to affect the integrity of the affected Oracle Database versions.

Vulnerability/
CVE-2016-0690

medium

21/4/2016

15/10/2024

CVE-2016-0690

First published: Thu Apr 21 2016(Updated: )

Unspecified vulnerability in the RDBMS Security component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows local users to affect integrity via unknown vectors, a different vulnerability than CVE-2016-0691.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle Database	=11.2.0.4
Oracle Database	=12.1.0.1
Oracle Database	=12.1.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-0690?
CVE-2016-0690 is classified with an unspecified severity level affecting the integrity of Oracle Database Server.
How do I fix CVE-2016-0690?
To fix CVE-2016-0690, apply the latest patches provided by Oracle for affected database versions.
Which versions of Oracle Database are affected by CVE-2016-0690?
CVE-2016-0690 affects Oracle Database versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.
Is CVE-2016-0690 a different vulnerability from CVE-2016-0691?
Yes, CVE-2016-0690 is considered a different vulnerability than CVE-2016-0691.
Can local users exploit CVE-2016-0690?
Yes, local users can exploit CVE-2016-0690 to affect the integrity of the affected Oracle Database versions.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/author
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
vendor/oracle
canonical/oracle database
version/oracle database/11.2.0.4
version/oracle database/12.1.0.1
version/oracle database/12.1.0.2

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-2016-0690?
CVE-2016-0690 is classified with an unspecified severity level affecting the integrity of Oracle Database Server.
How do I fix CVE-2016-0690?
To fix CVE-2016-0690, apply the latest patches provided by Oracle for affected database versions.
Which versions of Oracle Database are affected by CVE-2016-0690?
CVE-2016-0690 affects Oracle Database versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.
Is CVE-2016-0690 a different vulnerability from CVE-2016-0691?
Yes, CVE-2016-0690 is considered a different vulnerability than CVE-2016-0691.
Can local users exploit CVE-2016-0690?
Yes, local users can exploit CVE-2016-0690 to affect the integrity of the affected Oracle Database versions.