What is the severity of CVE-2017-10411?

CVE-2017-10411 is rated as having a high severity due to its potential for unauthenticated access to sensitive functionality.

How do I fix CVE-2017-10411?

To fix CVE-2017-10411, you should apply the latest security patches provided by Oracle for the affected versions.

What versions of Oracle Knowledge Management are affected by CVE-2017-10411?

CVE-2017-10411 affects versions 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6, and 12.2.7 of Oracle Knowledge Management.

Can CVE-2017-10411 be exploited remotely?

Yes, CVE-2017-10411 can be exploited remotely by an unauthenticated attacker, which poses a significant security risk.

Is there a workaround for CVE-2017-10411?

Currently, there are no known effective workarounds for CVE-2017-10411, and applying patches is the recommended mitigation.

Vulnerability/
CVE-2017-10411

high

8.2

19/10/2017

4/10/2024

CVE-2017-10411

First published: Thu Oct 19 2017(Updated: )

Vulnerability in the Oracle Knowledge Management component of Oracle E-Business Suite (subcomponent: User Interface). Supported versions that are affected are 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6 and 12.2.7. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Knowledge Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Knowledge Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Knowledge Management accessible data as well as unauthorized update, insert or delete access to some of Oracle Knowledge Management accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle Knowledge Management	=12.1.1
Oracle Knowledge Management	=12.1.2
Oracle Knowledge Management	=12.1.3
Oracle Knowledge Management	=12.2.3
Oracle Knowledge Management	=12.2.4
Oracle Knowledge Management	=12.2.5
Oracle Knowledge Management	=12.2.6
Oracle Knowledge Management	=12.2.7

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-10411?
CVE-2017-10411 is rated as having a high severity due to its potential for unauthenticated access to sensitive functionality.
How do I fix CVE-2017-10411?
To fix CVE-2017-10411, you should apply the latest security patches provided by Oracle for the affected versions.
What versions of Oracle Knowledge Management are affected by CVE-2017-10411?
CVE-2017-10411 affects versions 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6, and 12.2.7 of Oracle Knowledge Management.
Can CVE-2017-10411 be exploited remotely?
Yes, CVE-2017-10411 can be exploited remotely by an unauthenticated attacker, which poses a significant security risk.
Is there a workaround for CVE-2017-10411?
Currently, there are no known effective workarounds for CVE-2017-10411, and applying patches is the recommended mitigation.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/last-modified-date
agent/references
agent/severity
agent/remedy
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/oracle
canonical/oracle knowledge management
version/oracle knowledge management/12.1.1
version/oracle knowledge management/12.1.2
version/oracle knowledge management/12.1.3
version/oracle knowledge management/12.2.3
version/oracle knowledge management/12.2.4
version/oracle knowledge management/12.2.5
version/oracle knowledge management/12.2.6
version/oracle knowledge management/12.2.7