CVE-2024-36248: Detailed Vulnerability Analysis and Overview

CVE-2024-36248 Vulnerability Summary

API keys for some cloud services are hardcoded in the "main" binary. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].

Need help fixing CVEs? Check out our Step-by-Step Guide on How to Fix CVEs.

CVE-2024-36248: Detailed Information and External References

EPSS

0.00044

EPSS %

0.11891

References

0.00044

• https://global.sharp/products/copier/info/info_security_2024-05.html
• https://jp.sharp/business/print/information/info_security_2024-05.html
• https://jvn.jp/en/vu/JVNVU93051062/
• https://pierrekim.github.io/blog/2024-06-27-sharp-mfp-17-vulnerabilities.html
• https://www.toshibatec.co.jp/information/20240531_02.html
• https://www.toshibatec.com/information/20240531_02.html

CWE

CWE-798

CAPEC

0.00044

• Read Sensitive Constants Within an Executable: An adversary engages in activities to discover any sensitive constants present within the compiled code of an executable. These constants may include literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis.
• Try Common or Default Usernames and Passwords: An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.

CVSS3 Source

vultures@jpcert.or.jp

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N