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

CVE-2020-9365 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:H/I:N/A:N. EPSS exploitation probability: 7.1%.

Is there a public PoC exploit available for CVE-2020-9365?

Yes, a public proof-of-concept exploit is available for CVE-2020-9365. Prioritise patching immediately. EPSS: 7.1%.

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

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

Pure Ftpd CVE-2020-9365

HIGH

Out-of-bounds Read (CWE-125)

2020-02-24 cve@mitre.org

Buffer Overflow Information Disclosure Pure Ftpd Fedora

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:H/I:N/A:N

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:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Feb 24, 2020 - 16:15 nvd

HIGH 7.5

DescriptionNVD

An issue was discovered in Pure-FTPd 1.0.49. An out-of-bounds (OOB) read has been detected in the pure_strcmp function in utils.c.

AnalysisAI

An issue was discovered in Pure-FTPd 1.0.49. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Out-of-bounds Read vulnerability could allow attackers to read data from memory outside the intended buffer boundaries.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. An issue was discovered in Pure-FTPd 1.0.49. An out-of-bounds (OOB) read has been detected in the pure_strcmp function in utils.c. Affected products include: Pureftpd Pure-Ftpd, Fedoraproject Fedora.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.