# What is CVE-2017-16544?

> CVE-2017-16544 is a high-severity flaw (CVSS 8.8) in Busybox, published on 20 November 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 6.1%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-16544

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 57 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 8.8 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 6.1% (latest exploit-likelihood forecast)
- **Published:** 20 November 2017
- **Record last updated:** 9 June 2025
- **Main product:** Busybox
- **Affected products:** 6

## What is CVE-2017-16544? In plain terms

It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### The official description

In the add_match function in libbb/lineedit.c in BusyBox through 1.27.2, the tab autocomplete feature of the shell, used to get a list of filenames in a directory, does not sanitize filenames and results in executing any escape sequence in the terminal. This could potentially result in code execution, arbitrary file writes, or other attacks.

### What kind of flaw is it?

- CWE-94: Improper Control of Generation of Code ('Code Injection')

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: An ordinary user account
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`

## Is CVE-2017-16544 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 6.1%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 6.2%, 6.1%, 6.1%, 6.1%, 6.1%, 6.1%, 6.1%.

### Timeline

- 20 November 2017: Published
- 9 June 2025: Record last updated

### How Precursor Intelligence ranks it

CVE-2017-16544 scores **57 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2017-16544?

The published record lists 6 products.

- [Busybox](https://www.precursorintelligence.com/product/busybox/busybox) by [Busybox](https://www.precursorintelligence.com/vendors/busybox) (Application): up to 1.27.2
- [ESXi](https://www.precursorintelligence.com/product/vmware/esxi) by [VMware](https://www.precursorintelligence.com/vendors/vmware) (Operating system): 6.0, 6.0-1a, 6.0-1b, 6.0-1, 6.0-2, 6.0-3a, 6.0-3, 6.0-600-201504401, 6.0-600-201505401, 6.0-600-201507101, 6.0-600-201507102, 6.0-600-201507401, 6.0-600-201507402, 6.0-600-201507403, 6.0-600-201507404, 6.0-600-201507405, 6.0-600-201507406, 6.0-600-201507407, 6.0-600-201509101, 6.0-600-201509102, 6.0-600-201509201, 6.0-600-201509202, 6.0-600-201509203, 6.0-600-201509204, 6.0-600-201509205, 6.0-600-201509206, 6.0-600-201509207, 6.0-600-201509208, 6.0-600-201509209, 6.0-600-201509210, 6.0-600-201510401, 6.0-600-201511401, 6.0-600-201601101, 6.0-600-201601102, 6.0-600-201601401, 6.0-600-201601402, 6.0-600-201601403, 6.0-600-201601404, 6.0-600-201601405, 6.0-600-201602401 and 139 more
- [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 8.0, 9.0
- [Ubuntu Linux](https://www.precursorintelligence.com/product/canonical/ubuntu_linux) by [Canonical](https://www.precursorintelligence.com/vendors/canonical) (Operating system): 14.04, 16.04
- [N-Tron 702-W Firmware](https://www.precursorintelligence.com/product/redlion/n-tron_702-w_firmware) by [Redlion](https://www.precursorintelligence.com/vendors/redlion) (Operating system): all versions
- [N-Tron 702m12-W Firmware](https://www.precursorintelligence.com/product/redlion/n-tron_702m12-w_firmware) by [Redlion](https://www.precursorintelligence.com/vendors/redlion) (Operating system): all versions

## How do I fix CVE-2017-16544?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [git.busybox.net](https://git.busybox.net/busybox/commit/?id=c3797d40a1c57352192c6106cc0f435e7d9c11e8) (Patch, Vendor advisory)
- [packetstormsecurity.com](http://packetstormsecurity.com/files/154361/Cisco-Device-Hardcoded-Credentials-GNU-glibc-BusyBox.html) (Exploit, Third-party advisory, Vulnerability database)
- [packetstormsecurity.com](http://packetstormsecurity.com/files/154536/VMware-Security-Advisory-2019-0013.html) (Exploit, Third-party advisory, Vulnerability database)
- [packetstormsecurity.com](http://packetstormsecurity.com/files/167552/Nexans-FTTO-GigaSwitch-Outdated-Components-Hardcoded-Backdoor.html) (Exploit, Third-party advisory, Vulnerability database)
- [seclists.org](http://seclists.org/fulldisclosure/2019/Jun/18) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2019/Sep/7) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2020/Aug/20) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2020/Mar/15) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2020/Sep/6) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2021/Aug/21) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2021/Jan/39) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](http://seclists.org/fulldisclosure/2022/Jun/36) (Exploit, Mailing list, Third-party advisory)
- [vmware.com](http://www.vmware.com/security/advisories/VMSA-2019-0013.html) (Third-party advisory)
- [lists.debian.org](https://lists.debian.org/debian-lts-announce/2018/07/msg00037.html) (Mailing list, Third-party advisory)
- [lists.debian.org](https://lists.debian.org/debian-lts-announce/2021/02/msg00020.html) (Mailing list, Third-party advisory)
- [seclists.org](https://seclists.org/bugtraq/2019/Jun/14) (Exploit, Mailing list, Third-party advisory)
- [seclists.org](https://seclists.org/bugtraq/2019/Sep/7) (Exploit, Mailing list, Third-party advisory)
- [us-cert.cisa.gov](https://us-cert.cisa.gov/ics/advisories/icsa-20-240-01) (Third-party advisory, Government resource)
- [usn.ubuntu.com](https://usn.ubuntu.com/3935-1/) (Third-party advisory)
- [twistlock.com](https://www.twistlock.com/2017/11/20/cve-2017-16544-busybox-autocompletion-vulnerability/) (Third-party advisory)

## Questions

### What is CVE-2017-16544?

CVE-2017-16544 is a high-severity flaw in Busybox, published on 20 November 2017. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2017-16544?

It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2017-16544 is 57 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2017-16544 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 6.1%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2017-16544 affect?

For Busybox: up to 1.27.2. The record lists 6 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2017-16544?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2017-16544 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact