Skip to content
Fencer Intel
high 8.8

CVE-2020-9273 in the critical feed json

In ProFTPD 1.3.7, it is possible to corrupt the memory pool by interrupting the data transfer channel.

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

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

Summary

In ProFTPD 1.3.7, it is possible to corrupt the memory pool by interrupting the data transfer channel. This triggers a use-after-free in alloc_pool in pool.c, and possible remote code execution.

Patch / fix

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

debian advisories DEBIAN-CVE-2020-9273

  • 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-9273 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-9273 updated cvss 8.8

proftpd: use-after-free in alloc_pool in pool.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

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

CVSS scores

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

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.