# CVE-2017-5671: Privilege escalation in n/a

> Local attackers can gain root privileges on Honeywell industrial printers by exploiting a setuid Lua binary to overwrite system files.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pjq5-wxp4-r9pj

## What is CVE-2017-5671?

CVE-2017-5671 is a high-severity vulnerability in n/a, published on 29 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Honeywell Intermec PM23, PM42, PM43, PC23, PC43, PD43, and PC42 industrial printers before 10.11.013310 and 10.12.x before 10.12.013309 have /usr/bin/lua installed setuid to the itadmin account, which allows local users to conduct a BusyBox jailbreak attack and obtain root privileges by overwriting the /etc/shadow file.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-5671?

It affects 7 products.


Products: Honeywell Intermec Pc23 Firmware, Honeywell Intermec Pc42 Firmware, Honeywell Intermec Pc43 Firmware, Honeywell Intermec Pd43 Firmware, Honeywell Intermec Pm23 Firmware, Honeywell Intermec Pm42 Firmware, Honeywell Intermec Pm43 Firmware.

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

No fix has been published for CVE-2017-5671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5671 being exploited?

There is no known exploitation of CVE-2017-5671 in the wild and no public exploit code.

Public exploit code:

- Intermec PM43 Industrial Printer - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5671 and fix it if it is affected.

What it is: CVE-2017-5671 is a high-severity vulnerability in n/a, published on 29 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5671 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5671/ (Markdown: https://insights.sbomify.com/CVE-2017-5671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5671
- OSV: https://osv.dev/vulnerability/CVE-2017-5671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5671/
Summaries are generated and may contain mistakes; the official description above is the record.