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

CVE-2021-45720 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 1.2%.

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

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

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

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

Lru CVE-2021-45720

HIGH

Use After Free (CWE-416)

2021-12-26 cve@mitre.org

Use After Free Memory Corruption Information Disclosure Lru

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:N/I:N/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Dec 26, 2021 - 22:15 nvd

HIGH 7.5

DescriptionNVD

An issue was discovered in the lru crate before 0.7.1 for Rust. The iterators have a use-after-free, as demonstrated by an access after a pop operation.

AnalysisAI

An issue was discovered in the lru crate before 0.7.1 for Rust. Rated high severity (CVSS 7.5), 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. An issue was discovered in the lru crate before 0.7.1 for Rust. The iterators have a use-after-free, as demonstrated by an access after a pop operation. Affected products include: Lru Project Lru. Version information: before 0.7.1.

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.