CVE-2024-28955: Sharp Multiple MFPs (multifunction printers) · Incorrect Permissions
Affects Sharp Multiple MFPs (multifunction printers)Source CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
European organizations should implement strict physical and logical access controls to restrict local access to Sharp MFP devices. This includes securing device locations, enforcing user authentication for device access, and monitoring device usage logs for unauthorized access attempts. Network segmentation should isolate MFPs from sensitive network segments to limit potential lateral movement. Organizations should consult Sharp Corporation's official advisories for specific affected models and apply any available firmware updates or patches promptly once released. Additionally, disabling or restricting the generation of coredump files, if configurable, can reduce exposure. Regular security audits and vulnerability assessments of MFPs should be conducted to detect misconfigurations. Employing endpoint detection and response (EDR) solutions to monitor unusual activity on devices may also help detect exploitation attempts. Finally, educating staff about the risks of local device access and enforcing policies to prevent unauthorized use are critical.
Description
Affected devices create coredump files when crashed, storing them with world-readable permission. Any local user of the device can examine the coredump files, and research the memory contents. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].
References
- global.sharp/products/copier/info/info_security_2024-05.html (opens in a new tab)
- jp.sharp/business/print/information/info_security_2024-05.html (opens in a new tab)
- toshibatec.com/information/20240531_02.html (opens in a new tab)
- toshibatec.co.jp/information/20240531_02.html (opens in a new tab)
- jvn.jp/en/vu/JVNVU93051062/ (opens in a new tab)
- pierrekim.github.io/blog/2024-06-27-sharp-mfp-17-vulnerabilities.html (opens in a new tab)
- seclists.org/fulldisclosure/2024/Jul/0 (opens in a new tab)