CVE-2024-33610 in the critical feed json
"sessionlist.html" and "sys_trayentryreboot.html" are accessible with no authentication.
published last yr. modified 4mo ago also EUVD-2024-34577
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 50.5%
- EPSS 50.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
"sessionlist.html" and "sys_trayentryreboot.html" are accessible with no authentication. "sessionlist.html" provides logged-in users' session information including session cookies, and "sys_trayentryreboot.html" allows to reboot the device. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].
Is CVE-2024-33610 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
50.45% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- Sharp Corporation Multiple MFPs (multifunction printers)
- Toshiba Tec Corporation Multiple MFPs (multifunction printers)
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
References
- global.sharp /products/copier/info/info_security_2024-05.html
- jp.sharp /business/print/information/info_security_2024-05.html
- toshibatec.com /information/20240531_02.html
- toshibatec.co.jp /information/20240531_02.html
- jvn.jp /en/vu/JVNVU93051062/
- pierrekim.github.io /blog/2024-06-27-sharp-mfp-17-vulnerabilities.html
- seclists.org /fulldisclosure/2024/Jul/0
Sources
- CVE List CVE-2024-33610
- NVD CVE-2024-33610
Fencer Intel 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.