Skip to content
Fencer Intel
high 7.5

CVE-2020-9272 json

ProFTPD 1.3.7 has an out-of-bounds (OOB) read vulnerability in mod_cap via the cap_text.c cap_to_text function.

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

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

ProFTPD 1.3.7 has an out-of-bounds (OOB) read vulnerability in mod_cap via the cap_text.c cap_to_text function.

Patch / fix

  • proftpd proftpd 1.3.6c
  • siemens simatic_net_cp_1543-1_firmware 3.0
  • proftpd-dfsg Debian 14, Debian 13, Debian 12 1.3.6c-1

debian advisories DEBIAN-CVE-2020-9272

  • proftpd openSUSE Tumbleweed 1.3.6e-1.10
  • proftpd Package Hub 15 SP1, Package Hub 15, openSUSE Leap 15.1 1.3.6c-bp151.4.9.1

opensuse advisories openSUSE-SU-2024:11196-1openSUSE-SU-2020:0273-1

Is CVE-2020-9272 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-9272 updated cvss 7.5

proftpd: out-of-bounds read in cap_to_text in cap_text.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

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

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.