What is the CVSS score of CVE-2021-23758?

CVE-2021-23758 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: 88.8%.

Is there a public PoC exploit available for CVE-2021-23758?

Yes, a public proof-of-concept exploit is available for CVE-2021-23758. Prioritise patching immediately. EPSS: 88.8%.

Is there a patch available for CVE-2021-23758?

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

Ajaxpro 2 CVE-2021-23758

CRITICAL

Deserialization of Untrusted Data (CWE-502)

2021-12-03 report@snyk.io

Deserialization RCE Ajaxpro 2

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

Dec 03, 2021 - 20:15 nvd

CRITICAL 9.8

DescriptionNVD

AnalysisAI

All versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity.

Technical ContextAI

This vulnerability is classified as Deserialization of Untrusted Data (CWE-502), which allows attackers to execute arbitrary code through malicious serialized objects. All versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution. Affected products include: Ajaxpro.2 Project Ajaxpro.2.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Avoid deserializing untrusted data. Use safe serialization formats (JSON). Implement integrity checks and type allowlists.