CVE-2024-36251: Sharp Multiple MFPs (multifunction printers) · Out-of-bounds Read
Affects Sharp Multiple MFPs (multifunction printers)Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 3.4% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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
1. Apply official patches or firmware updates from Sharp Corporation as soon as they are released to address CVE-2024-36251. 2. Restrict network access to the web management interface of Sharp MFPs by implementing network segmentation and firewall rules that limit access to trusted administrators only. 3. Disable or restrict remote management features if not required, reducing the attack surface. 4. Monitor network traffic for unusual or malformed HTTP requests targeting billcodedef_sub_sel.html or other printer web interface endpoints, using intrusion detection/prevention systems (IDS/IPS). 5. Implement strict input validation and anomaly detection on network devices to detect potential exploitation attempts. 6. Conduct regular security audits of multifunction printers and related infrastructure to ensure configurations follow best practices. 7. Educate IT staff about this vulnerability and ensure incident response plans include steps for printer-related denial-of-service events. 8. Consider isolating multifunction printers on dedicated VLANs with limited access to critical network segments to contain potential impacts. 9. Maintain an inventory of all Sharp MFP devices to quickly identify and remediate affected units. These steps go beyond generic advice by focusing on network-level controls, monitoring, and operational readiness specific to multifunction printer environments.
Description
The web interface of the affected devices process some crafted HTTP requests improperly, leading to a device crash. More precisely, a crafted parameter to billcodedef_sub_sel.html is not processed properly and device-crash happens. 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)