CVE-2019-11366

What it is

An issue was discovered in atftpd in atftp 0.7.1. It does not lock the thread_list_mutex mutex before assigning the current thread data structure. As a result, the daemon is vulnerable to a denial of service attack due to a NULL pointer dereference. If thread_data is NULL when assigned to current, and modified by another thread before a certain tftpd_list.c check, there is a crash when dereferencing current->next.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

2.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-04-20 13:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:12 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.1% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-04-20 13:29 UTC

Last modified

2026-06-17 02:12 UTC

Exploit probability

2.1% · EPSS, next 30 days

Weakness

CWE-476 · NULL pointer dereference

Record status

Modified

Affected

• Atftp Project Atftp 0.7.1

Attack profile CVSS 3.0 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-11366.md and follow it. Check whether this project is affected by CVE-2019-11366. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge