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
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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.
- agent/references
- agent/type
- agent/softwarecombine
- agent/author
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- 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