Skip to content
Fencer Vulns
medium 5.3

CVE-2024-45842 json

Sharp and Toshiba Tec MFPs improperly process URI data in HTTP PUT requests resulting in a path Traversal vulnerability.

published 2024-10-25 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-41569

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

Sharp 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.

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Sharp Corporation Sharp Digital Full-color MFPs and Monochrome MFPs
  • Toshiba Tec Corporation e-STUDIO 908
  • Toshiba Tec Corporation e-STUDIO 1058
  • Toshiba Tec Corporation e-STUDIO 1208
  • toshibatec e-studio-1058_firmware
  • sharp bp-90c80_firmware
  • sharp bp-70c65_firmware
  • sharp mx-8081_firmware
  • sharp mx-6071s_firmware
  • sharp bp-30c25_firmware
  • sharp mx-7580n_firmware
  • sharp mx-8090n_firmware
  • sharp mx-6070v_firmware
  • toshibatec e-studio-1208_firmware
  • sharp bp-c545wd_firmware
  • sharp mx-c304wh_firmware
  • sharp bp-70m90_firmware
  • sharp bp-70m65_firmware
  • sharp mx-m1206_firmware
  • sharp mx-m7570_firmware
  • sharp mx-m6071s_firmware
  • sharp bp-30m35t_firmware
  • sharp mx-b476wh_firmware
  • sharp mx-m905_firmware
  • sharp mx-m6070_firmware
  • sharp bp-b550wd_firmware
  • sharp mx-b455wz_firmware
  • toshibatec e-studio-908_firmware

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.