Path TraversalWeakness · CWE-22

CVE-2024-27145

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
The Toshiba printers provide several ways to upload files using the admin web interface. An attacker can remotely compromise any Toshiba printer. An attacker can overwrite any insecure files. This vulnerability can be executed in combination with other vulnerabilities and difficult to execute alone. So, the CVSS score for this vulnerability alone is lower than the score listed in the "Base Score" of this vulnerability. For detail on related other vulnerabilities, please ask to the below contact point. https://www.toshibatec.com/contacts/products/ As for the affected products/models/versions, see the reference URL.

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

Toshiba printers contain a file upload vulnerability in their admin web interface that allows remote attackers to overwrite files on the device. This vulnerability enables remote compromise of affected printers and is typically exploited in combination with other vulnerabilities to achieve full system control.

MitigationApply vendor-supplied firmware patches when available and restrict access to the admin web interface to trusted networks or IP addresses until patches can be deployed.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Toshiba printer model
    Access the device web interface, check the device label, or query the device via SNMP/embedded web server to confirm the exact model number
    Affected if The device is a Toshiba printer with an admin web interface
  2. Locate the installed firmware version
    Log into the admin web interface and navigate to the System/Status or Settings/About page to find the firmware version string, or query the device via SNMP using the sysDescr OID
    Affected if The firmware version cannot be confirmed or is earlier than the vendor patched version
  3. Verify admin web interface exposure
    Check network firewall rules, port scans, or device network settings to determine if TCP ports 80/443 (or custom admin ports) are accessible from untrusted or external networks
    Affected if The admin web interface is reachable from untrusted networks or the internet
  4. Inspect for unauthorized file modifications
    Review the device configuration backups or log files via the admin interface for unexpected file uploads, new web shells, or modified system files
    Affected if Unexpected files exist in web directories or configuration changes are present that were not made by authorized administrators
  5. Check for evidence of remote access
    Examine device logs for unusual IP addresses, failed authentication attempts from external sources, or unexpected administrative actions
    Affected if Logs show administrative actions from unknown IP addresses or anomalous authentication patterns

The device is affected if it is a Toshiba printer with an admin web interface that is exposed to untrusted networks and runs firmware that has not been patched by Toshiba for this file upload vulnerability.

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-supplied firmware patches when available and restrict access to the admin web interface to trusted networks or IP addresses until patches can be deployed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2024-27145 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