dbcve.org
Cl4nx J Plus FirmwareOperating system · Sato

CVE-2023-5327

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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
A vulnerability was found in SATO CL4NX-J Plus 1.13.2-u455_r2. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /rest/dir/. The manipulation of the argument full leads to path traversal. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-241028.

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 · high confidence

A path traversal vulnerability in the SATO CL4NX-J Plus printer firmware (version 1.13.2-u455_r2) allows local network attackers to access arbitrary files via the /rest/dir/ API endpoint by manipulating the 'full' parameter with directory traversal sequences (e.g., ../../). The vulnerability requires network adjacency but no authentication.

MitigationApply vendor firmware patch when available; until then, restrict network access to the printer's management interfaces to trusted IPs only via network segmentation or firewall rules.

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
Cl4nx J Plus FirmwareOperating system
Affected:= 1.13.2-u455_r2

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 printer model
    Access the printer's web interface (if available) or use network scanning tools (e.g., nmap, Angry IP Scanner) to identify the device as SATO CL4NX-J Plus. Check the HTTP server banner or SNMP sysDescr for model identification.
    Affected if The device is a SATO CL4NX-J Plus model.
  2. Check the installed firmware version
    Log into the printer's web management interface and navigate to the System Settings or Firmware Information page. Alternatively, access the /rest/info/firmware or similar endpoint, or use SNMP OIDs to retrieve the firmware version.
    Affected if The firmware version is exactly 1.13.2-u455_r2.
  3. Verify the /rest/dir/ API endpoint is reachable
    From a local network host, attempt an HTTP GET request to http://<printer-ip>/rest/dir/ . If the endpoint responds (even with an error), it indicates the API is enabled and reachable.
    Affected if The /rest/dir/ endpoint returns an HTTP response (200, 400, or similar) indicating it is accessible.
  4. Assess network exposure of the printer management interface
    Review network configuration to determine if the printer's web interface (ports 80/443) is exposed to untrusted networks. Check firewall rules, VLAN placement, and whether the printer is on a shared or guest network segment.
    Affected if The printer management interface is accessible from network segments containing untrusted or unknown hosts.
  5. Test for directory traversal vulnerability (optional confirmation)
    Send a crafted HTTP GET request to /rest/dir/ with a 'full' parameter containing directory traversal sequences such as ../../etc/passwd or ../../etc/shadow . Compare the response to a normal request. If the response contains contents of system files outside the web root, the vulnerability is present.
    Affected if The response contains contents of files outside the expected web root directory (e.g., /etc/passwd contents).

A user is affected if the device is a SATO CL4NX-J Plus running firmware version 1.13.2-u455_r2 with the /rest/dir/ endpoint accessible from an untrusted network segment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; until then, restrict network access to the printer's management interfaces to trusted IPs only via network segmentation or firewall rules.

Fix this in Cl4nx J Plus Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5327 — 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-5327 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