What is the severity of CVE-2016-3474?

CVE-2016-3474 is classified as a security vulnerability that could lead to potential loss of confidentiality.

How do I fix CVE-2016-3474?

To fix CVE-2016-3474, it is recommended to apply the latest security patches provided by Oracle for the affected versions.

Which versions of Oracle BI Publisher are affected by CVE-2016-3474?

CVE-2016-3474 affects Oracle Business Intelligence Publisher versions 11.1.1.7.0, 11.1.1.9.0, and 12.2.1.0.0.

Can CVE-2016-3474 be exploited remotely?

Yes, CVE-2016-3474 can be exploited remotely by attackers to impact confidentiality.

Is there a known workaround for CVE-2016-3474?

There are no specific workarounds for CVE-2016-3474; applying the necessary security updates is the best approach.

Vulnerability/
CVE-2016-3474

medium

4.3

21/7/2016

11/10/2024

CVE-2016-3474

First published: Thu Jul 21 2016(Updated: )

Unspecified vulnerability in the BI Publisher (formerly XML Publisher) component in Oracle Fusion Middleware 11.1.1.7.0, 11.1.1.9.0, and 12.2.1.0.0 allows remote attackers to affect confidentiality via vectors related to Security.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle Business Intelligence Publisher	=11.1.1.7.0
Oracle Business Intelligence Publisher	=11.1.1.9.0
Oracle Business Intelligence Publisher	=12.2.1.0.0

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-3474?
CVE-2016-3474 is classified as a security vulnerability that could lead to potential loss of confidentiality.
How do I fix CVE-2016-3474?
To fix CVE-2016-3474, it is recommended to apply the latest security patches provided by Oracle for the affected versions.
Which versions of Oracle BI Publisher are affected by CVE-2016-3474?
CVE-2016-3474 affects Oracle Business Intelligence Publisher versions 11.1.1.7.0, 11.1.1.9.0, and 12.2.1.0.0.
Can CVE-2016-3474 be exploited remotely?
Yes, CVE-2016-3474 can be exploited remotely by attackers to impact confidentiality.
Is there a known workaround for CVE-2016-3474?
There are no specific workarounds for CVE-2016-3474; applying the necessary security updates is the best approach.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/severity
agent/remedy
agent/author
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 business intelligence publisher
version/oracle business intelligence publisher/11.1.1.7.0
version/oracle business intelligence publisher/11.1.1.9.0
version/oracle business intelligence publisher/12.2.1.0.0

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-3474?
CVE-2016-3474 is classified as a security vulnerability that could lead to potential loss of confidentiality.
How do I fix CVE-2016-3474?
To fix CVE-2016-3474, it is recommended to apply the latest security patches provided by Oracle for the affected versions.
Which versions of Oracle BI Publisher are affected by CVE-2016-3474?
CVE-2016-3474 affects Oracle Business Intelligence Publisher versions 11.1.1.7.0, 11.1.1.9.0, and 12.2.1.0.0.
Can CVE-2016-3474 be exploited remotely?
Yes, CVE-2016-3474 can be exploited remotely by attackers to impact confidentiality.
Is there a known workaround for CVE-2016-3474?
There are no specific workarounds for CVE-2016-3474; applying the necessary security updates is the best approach.