What is the CVSS score of CVE-2023-38669?

CVE-2023-38669 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.7%.

Is there a public PoC exploit available for CVE-2023-38669?

Yes, a public proof-of-concept exploit is available for CVE-2023-38669. Prioritise patching immediately. EPSS: 0.7%.

Is there a patch available for CVE-2023-38669?

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

Paddlepaddle CVE-2023-38669

CRITICAL

Use After Free (CWE-416)

2023-07-26 paddle-security@baidu.com

Use After Free Denial Of Service Memory Corruption Paddlepaddle

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jul 26, 2023 - 10:15 nvd

CRITICAL 9.8

DescriptionNVD

Use after free in paddle.diagonal in PaddlePaddle before 2.5.0. This resulted in a potentially exploitable condition.

AnalysisAI

Use after free in paddle.diagonal in PaddlePaddle before 2.5.0. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Use After Free (CWE-416), which allows attackers to access freed memory to execute arbitrary code or crash the application. Use after free in paddle.diagonal in PaddlePaddle before 2.5.0. This resulted in a potentially exploitable condition. Affected products include: Paddlepaddle. Version information: before 2.5.0..

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use smart pointers or garbage-collected languages. Set pointers to NULL after freeing. Enable memory sanitizers.