CVE-2024-34162 json
The web interface of the affected devices is designed to hide the LDAP credentials even for administrative users.
published last yr. modified 4mo ago also EUVD-2024-35155
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
The web interface of the affected devices is designed to hide the LDAP credentials even for administrative users. But configuring LDAP authentication to "SIMPLE", the device communicates with the LDAP server in clear-text. The LDAP password can be retrieved from this clear-text communication. 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-34162 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
- partial
- Assessed
- last yr.
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-11).
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:L/I:N/A:N |
Affected products
- Sharp Corporation Multiple MFPs (multifunction printers)
- Toshiba Tec Corporation Multiple MFPs (multifunction printers)
Classification
- Weakness
-
- CWE-767 Access to Critical Private Variable via Public Method
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-34162
- NVD CVE-2024-34162
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.