dbcve.org
Pm43 FirmwareOperating system · Honeywell

CVE-2023-3712

HIGH · 7.8 CVSS v3.1 Published 2023-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Files or Directories Accessible to External Parties vulnerability in Honeywell PM43 on 32 bit, ARM (Printer web page modules) allows Privilege Escalation.This issue affects PM43 versions prior to P10.19.050004.  Update to the latest available firmware version of the respective printers to version MR19.5 (e.g. P10.19.050006).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Honeywell PM43 printer's web interface contains a vulnerability where certain files or directories are accessible to external parties. This exposure allows an attacker to potentially access sensitive files or configuration data through the web page modules, which can then be leveraged for privilege escalation to gain elevated access on the device.

MitigationUpdate the PM43 printer firmware to version P10.19.050006 (MR19.5) or later to remediate the vulnerability. Verify the update in a staging environment before production deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pm43 FirmwareOperating system
Affected:< p10.19.050004

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed firmware version
    Access the printer's web interface or use the printer's control panel menu to navigate to the system information or firmware version section. Alternatively, print a configuration label which typically displays the firmware version.
    Affected if The displayed firmware version is less than p10.19.050004 (for example, p10.19.xxxxx where the number is below 050004).
  2. Verify the web interface is enabled
    Attempt to access the printer's web interface by entering the printer's IP address in a web browser. Confirm the login page or status page loads successfully.
    Affected if The web interface is accessible and responds to HTTP/HTTPS requests, indicating it is enabled on the device.
  3. Check for unauthorized file access via web paths
    Using a web browser or curl command, attempt to access common web paths such as /.. or other directory traversal patterns on the printer's web interface. Observe whether the server returns file contents or directory listings instead of rejecting the request.
    Affected if The web server returns file contents, configuration data, or directory listings when accessing paths outside the normal web root, indicating the file disclosure vulnerability is present.

A device is affected if it runs firmware version p10.19.050004 or earlier and has its web interface enabled, allowing external access to sensitive files or directories through the web page modules.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the PM43 printer firmware to version P10.19.050006 (MR19.5) or later to remediate the vulnerability. Verify the update in a staging environment before production deployment.

Recommended fix High confidence

P10.19.050006 (MR19.5)

  1. Access the Honeywell support website or authorized partner portal to obtain the firmware file
  2. Locate and download the PM43 firmware version P10.19.050006 (MR19.5) or later from hsmftp.honeywell.com or www.honeywell.com
  3. Log into the PM43 printer web management interface using administrator credentials
  4. Navigate to the firmware upgrade or system maintenance section of the web interface
  5. Upload the downloaded firmware file (P10.19.050006)
  6. Initiate the firmware upgrade process and wait for completion
  7. Verify the firmware has been successfully installed by checking the version in the printer settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pm43 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3712 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data