Skip to content
Fencer Intel
high 7.5

CVE-2020-9365 json

An issue was discovered in Pure-FTPd 1.0.49.

published 6y ago modified 4mo ago also EUVD-2020-30186

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.1%
EPSS 7.1% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • pure-ftpd Debian 13, Debian 12 1.0.49-3

debian advisories DEBIAN-CVE-2020-9365

  • pure-ftpd openSUSE Tumbleweed 1.0.50-1.1

opensuse advisories openSUSE-SU-2024:11773-1

  • pure-ftpd Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 1.0.49-r1

alpine advisories ALPINE-CVE-2020-9365

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-9365 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-9365 updated cvss 7.5

pure-ftpd: OOB read in pure_strcmp function in utils.c

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.11% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Pure-FTPd 1.0.24 - Security Vulnerability nuclei detection template

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.