{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39903 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-39903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39903 is a medium-severity vulnerability in n/a, published on 7 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-39903 and fix it if it is affected.\n\nWhat it is: CVE-2023-39903 is a medium-severity vulnerability in n/a, published on 7 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-39903 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-39903/ (Markdown: https://insights.sbomify.com/CVE-2023-39903/index.md)","id":"CVE-2023-39903","markdown":"https://insights.sbomify.com/CVE-2023-39903/index.md","name":"CVE-2023-39903","record":{"aliases":["GHSA-h594-v489-8m9p"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Fujitsu ISM","requires_auth":"low_privilege","summary":"A privileged attacker can read cleartext credentials from log files if firmware repository features are enabled and specific characters are used in passwords.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"software_infrastructure_manager","vendor":"fujitsu"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:N/C:H/I:N/PR:L/S:C/UI:R","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"An issue was discovered in Fujitsu Software Infrastructure Manager (ISM) before 2.8.0.061. The ismsnap component (in this specific case at /var/log/fujitsu/ServerViewSuite/ism/FirmwareManagement/FirmwareManagement.log) allows insecure collection and storage of authorization credentials in cleartext. That occurs when users perform any ISM Firmware Repository Address setup test (Test the Connection), or regularly authorize against an already configured remote firmware repository site, as set up in ISM Firmware Repository Address. A privileged attacker is therefore able to potentially gather the associated ismsnap maintenance data, in the same manner as a trusted party allowed to export ismsnap data from ISM. The preconditions for an ISM installation to be generally vulnerable are that the Download Firmware (Firmware Repository Server) function is enabled and configured, and that the character \\ (backslash) is used in a user credential (i.e., user/ID or password) of the remote proxy host / firmware repository server. NOTE: this may overlap CVE-2023-39379.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2023-39903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2023-39908"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-39902"},"products":["n/a"],"published":"2023-08-07","related":[{"cvss_score":7.5,"headline":"Information disclosure in Fujitsu Software Infrastructure Manager Advanced Edition","id":"CVE-2023-39379","kev_date_added":null,"published":"2023-08-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-15","vendors":["n/a"]},"summary":"A privileged attacker can read cleartext credentials from log files if firmware repository features are enabled and specific characters are used in passwords.","url":"https://insights.sbomify.com/CVE-2023-39903/"}