CVE-2020-2550: Medium severity ORACLE WebLogic Server vulnerability
Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: WLS Core Components). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle WebLogic Server executes to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data as well as unauthorized update, insert or delete access to some of Oracle WebLogic Server accessible data. CVSS 3.0 Base Score 5.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Oracle WebLogic Server (WLS Core Components)to a version that resolves this vulnerability.Fixed in 10.3.6.0.0 - Upgrade
Upgrade
Oracle WebLogic Server (WLS Core Components)to a version that resolves this vulnerability.Fixed in 12.1.3.0.0 - Upgrade
Upgrade
Oracle WebLogic Server (WLS Core Components)to a version that resolves this vulnerability.Fixed in 12.2.1.3.0 - Upgrade
Upgrade
Oracle WebLogic Server (WLS Core Components)to a version that resolves this vulnerability.Fixed in 12.2.1.4.0
Event History
Frequently Asked Questions
What is the severity of CVE-2020-2550?
CVE-2020-2550 is considered a critical vulnerability due to its potential for exploitation by high privileged attackers.
Which versions of Oracle WebLogic Server are affected by CVE-2020-2550?
CVE-2020-2550 affects Oracle WebLogic Server 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, and 12.2.1.4.0.
How do I fix CVE-2020-2550?
To fix CVE-2020-2550, upgrade to the latest version of Oracle WebLogic Server as recommended by Oracle.
What can attackers do with CVE-2020-2550?
Attackers can exploit CVE-2020-2550 to gain unauthorized access to sensitive information or perform privileged actions.
Is there any workaround for CVE-2020-2550?
There are no known workarounds for CVE-2020-2550, making patching the only effective solution.