What is the severity of CVE-2016-3609?

The severity of CVE-2016-3609 is critical as it affects confidentiality, integrity, and availability for Oracle Database Server components.

How do I fix CVE-2016-3609?

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

Who is affected by CVE-2016-3609?

CVE-2016-3609 affects remote authenticated users of Oracle Database Server versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.

What components are impacted by CVE-2016-3609?

CVE-2016-3609 impacts the OJVM component within the Oracle Database Server.

Can CVE-2016-3609 be exploited remotely?

Yes, CVE-2016-3609 can be exploited remotely by authenticated users.

Vulnerability/
CVE-2016-3609

critical

21/7/2016

11/10/2024

CVE-2016-3609

First published: Thu Jul 21 2016(Updated: )

Unspecified vulnerability in the OJVM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors.

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

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-3609?
The severity of CVE-2016-3609 is critical as it affects confidentiality, integrity, and availability for Oracle Database Server components.
How do I fix CVE-2016-3609?
To fix CVE-2016-3609, apply the latest patches or updates provided by Oracle for affected database versions.
Who is affected by CVE-2016-3609?
CVE-2016-3609 affects remote authenticated users of Oracle Database Server versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.
What components are impacted by CVE-2016-3609?
CVE-2016-3609 impacts the OJVM component within the Oracle Database Server.
Can CVE-2016-3609 be exploited remotely?
Yes, CVE-2016-3609 can be exploited remotely by authenticated users.

collector/nvd-index
agent/type
agent/references
agent/softwarecombine
agent/author
agent/remedy
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-3609?
The severity of CVE-2016-3609 is critical as it affects confidentiality, integrity, and availability for Oracle Database Server components.
How do I fix CVE-2016-3609?
To fix CVE-2016-3609, apply the latest patches or updates provided by Oracle for affected database versions.
Who is affected by CVE-2016-3609?
CVE-2016-3609 affects remote authenticated users of Oracle Database Server versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.
What components are impacted by CVE-2016-3609?
CVE-2016-3609 impacts the OJVM component within the Oracle Database Server.
Can CVE-2016-3609 be exploited remotely?
Yes, CVE-2016-3609 can be exploited remotely by authenticated users.