What is the CVSS score of CVE-2020-2569?

CVE-2020-2569 has a CVSS 3.1 base score of 3.9 (Low). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L. EPSS exploitation probability: 0.3%.

Is there a patch available for CVE-2020-2569?

Yes, a patch is available for CVE-2020-2569. Update the affected software to the latest version immediately.

Applications Dba CVE-2020-2569

LOW

2020-01-15 secalert_us@oracle.com

Denial Of Service Oracle Applications Dba

3.9

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

3.9 LOW

AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

Low

Lifecycle Timeline

CVE Published

Jan 15, 2020 - 17:15 nvd

LOW 3.9

DescriptionNVD

Vulnerability in the Oracle Applications DBA component of Oracle Database Server. Supported versions that are affected are 11.2.0.4, 12.1.0.2, 12.2.0.1, 18c and 19c. Easily exploitable vulnerability allows low privileged attacker having Local Logon privilege with logon to the infrastructure where Oracle Applications DBA executes to compromise Oracle Applications DBA. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Applications DBA accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Applications DBA. CVSS 3.0 Base Score 3.9 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L).

AnalysisAI

Vulnerability in the Oracle Applications DBA component of Oracle Database Server. Rated low severity (CVSS 3.9), this vulnerability is low attack complexity.

Technical ContextAI

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.