Skip to content
Fencer Vulns
critical 9.8

CVE-2019-11365 json

An issue was discovered in atftpd in atftp 0.7.1.

published 2019-04-20 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3043

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.3%
EPSS 4.3% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

An issue was discovered in atftpd in atftp 0.7.1. A remote attacker may send a crafted packet triggering a stack-based buffer overflow due to an insecurely implemented strncpy call. The vulnerability is triggered by sending an error packet of 3 bytes or fewer. There are multiple instances of this vulnerable strncpy pattern within the code base, specifically within tftpd_file.c, tftp_file.c, tftpd_mtftp.c, and tftp_mtftp.c.

Patch / fix

  • atftp Debian 14, Debian 13, Debian 12 0.7.git20120829-3.1

debian advisories DEBIAN-CVE-2019-11365

  • atftp Ubuntu 16.04 LTS 0.7.git20120829-3.1~0.16.04.1
  • atftp Ubuntu 18.04 LTS 0.7.git20120829-3.1~0.18.04.1

ubuntu advisories UBUNTU-CVE-2019-11365

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • atftp SLES 11 SP4-LTSS, SLE Point of Sale 11 SP3 0.7.0-135.23.3.1
  • atftp SLES for SAP 12 SP4, SLES for SAP 12 SP3, SLES for SAP 12 SP2 +11 more 0.7.0-160.8.1

suse advisories SUSE-SU-2019:14033-1SUSE-SU-2019:1091-1

  • atftp openSUSE Tumbleweed 0.7.5-1.1

opensuse advisories openSUSE-SU-2024:10636-1

Exploit prediction

4.29% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • pulsesecurity.co.nz https://pulsesecurity.co.nz/advisories/atftpd-multiple-vulnerabilities referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Vulns 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.