CVE-2024-45842
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 · uneditedSharp and Toshiba Tec MFPs improperly process URI data in HTTP PUT requests resulting in a path Traversal vulnerability. Unintended internal files may be retrieved when processing crafted HTTP requests.
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 confidenceSharp and Toshiba Tec Multi-Function Printers (MFPs) contain a path traversal vulnerability in their web interface. Attackers can craft malicious URI data in HTTP PUT requests to access files outside the intended web root, potentially exposing sensitive internal documents or configuration files.
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<= t1.01.h4.00<= t1.01.h4.00<= t2.12.h3.00all versionsall versionsall versionsall versionsall versionsCVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the MFP web interface is accessibleAttempt to access the printer's web interface via HTTP (port 80/443) or HTTPS using the printer's IP address. If a login page or web console loads, the web interface is enabled.Affected if The web interface is enabled and reachable over the network - this is required for the path traversal attack to be exploitable.
-
Identify the device model and firmware versionLog into the web interface and navigate to the System Settings, Device Information, or Status page. Look for fields labeled 'Firmware Version', 'Model Name', or 'Device Name'. Alternatively, check the main landing page or footer for version information.Affected if The device model matches Sharp BP 70c45, 70c55, 70c65, 90c70, 90c80 or Toshiba Tec E Studio908, 1208, 1058, and the firmware version is at or below the affected thresholds.
-
Compare installed firmware against affected versionsFor Toshiba Tec devices: note the exact firmware string (e.g., t1.01.h4.00 or t2.12.h3.00) and verify it is <= t1.01.h4.00 for E Studio1058/1208, or <= t2.12.h3.00 for E Studio908. For Sharp BP devices: all listed firmware versions (70c45, 70c55, 70c65, 90c70, 90c80) are affected regardless of version.Affected if The identified firmware version falls within or below the specified version ranges, or the device is a Sharp BP model listed as 'all versions' affected.
-
Verify HTTP PUT method is allowed on the web serverSend a test HTTP PUT request to the device's web interface (e.g., PUT /../../etc/passwd HTTP/1.1) using a tool like curl or Burp Suite. A response other than '405 Method Not Allowed' indicates PUT is accepted.Affected if The web server accepts PUT requests - this is the attack vector required to exploit the path traversal vulnerability.
Your environment is affected if the MFP has its web interface enabled, is network-accessible, and runs a firmware version matching the affected Sharp BP models (any version) or Toshiba Tec models at or below the specified version thresholds.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict network access to MFP web management interfaces, apply vendor firmware updates when available, and consider placing MFPs in isolated network segments to reduce exposure.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45842 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45842 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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