CVE-2024-36251
CVE-2024-36251 Vulnerability Analysis & Exploit Intelligence
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].
Published Updated Sources: cvelistV5, jpcert
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
PoC
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (2)
Products (23)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-125
References
7 on the record
- global.sharp/products/copier/info/info_security_2024-05.html
reference
- jp.sharp/business/print/information/info_security_2024-05.html
reference
- www.toshibatec.com/information/20240531_02.html
reference
- www.toshibatec.co.jp/information/20240531_02.html
reference
- jvn.jp/en/vu/JVNVU93051062/
reference
- pierrekim.github.io/blog/2024-06-27-sharp-mfp-17-vulnerabilities.html
reference
- seclists.org/fulldisclosure/2024/Jul/0
reference
Elsewhere on this site
- sharpevery CVE for this vendor
- toshiba tecevery CVE for this vendor
- CWE-125other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.