TFTP Service Accessible
A TFTP server, which has no authentication, can be reached from untrusted networks, so anyone who can guess file names can download, and sometimes upload, the files it serves.
| Severity | Medium |
| CVSS 3.1 | 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-552: Files or Directories Accessible to External Parties |
| OWASP Top 10 | A01:2025 Broken Access Control |
| MITRE ATT&CK | T1602.002 Network Device Configuration Dump, T1552.001 Credentials In Files, T1542.005 TFTP Boot |
| Category | Broken Access Control |
Description
A Trivial File Transfer Protocol (TFTP) server can be reached from networks that have no need to use it. TFTP has no authentication or encryption: any client that can reach UDP 69 and name a file can download it, and servers configured to accept writes will also accept uploads. TFTP is commonly used to store network device configurations and operating system images, to provision IP phones and other devices, and to serve network boot files, so the files it holds are often sensitive.
Files retrieved from the server often contain credentials and network details, such as device passwords, SNMP community strings, VPN keys and provisioning secrets, which an attacker can use to access network devices or other systems. Where the server accepts uploads, an attacker may be able to replace configuration files or boot images that devices load, which could give them control of those devices the next time they start or are provisioned. How serious this is depends on the files the server holds and whether it is writable: a read-only server holding nothing sensitive presents little risk.
TFTP has no directory listing, so the issue is confirmed by requesting likely file names, such as device configuration backups, phone provisioning files or boot files, with a TFTP client or tools such as the Nmap tftp-enum script, and by checking whether uploads are accepted. Scanners report it as a TFTP server detected or as files retrievable from a TFTP server.
Remediation
Remove the service where possible and restrict it where it is needed:
- Disable TFTP servers that are not needed, including those left running after a one-off firmware upgrade or configuration backup.
- Where TFTP is required, for example for network boot or phone provisioning, restrict UDP 69 with firewall rules and access lists to the devices that use it, and keep the server on a management or provisioning network.
- Run the server read-only and confined to a dedicated directory, and remove configuration backups and other sensitive files from it.
- Move configuration transfers to authenticated, encrypted protocols such as SCP, SFTP or HTTPS, and use HTTPS-based provisioning where devices support it.
- Change any credentials found in files that were exposed.
Confirm the fix by requesting known file names from an untrusted network and checking that no response is received.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.