{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-1882 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1882 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1882 is a medium-severity vulnerability in IBM Spectrum Protect, published on 8 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1882 and fix it if it is affected.\n\nWhat it is: CVE-2018-1882 is a medium-severity vulnerability in IBM Spectrum Protect, published on 8 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1882 in the wild and no public exploit code.\n\nAffected product: IBM Spectrum Protect. 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-2018-1882/ (Markdown: https://insights.sbomify.com/CVE-2018-1882/index.md)","id":"CVE-2018-1882","markdown":"https://insights.sbomify.com/CVE-2018-1882/index.md","name":"CVE-2018-1882","record":{"aliases":["GHSA-p469-7gqp-fp24"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"IBM Spectrum Protect","requires_auth":"low_privilege","summary":"Attackers with access to trace files can read node passwords in plain text in specific IBM Spectrum Protect configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"spectrum_protect_backup-archive_client","vendor":"ibm"},{"product":"spectrum_protect_for_virtual_environments","vendor":"ibm"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/UI:N/S:U/C:H/AC:H/I:N/PR:L/A:N/RC:C/E:U/RL:O","version":"3.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"In a certain atypical IBM Spectrum Protect 7.1 and 8.1 configurations, the node password could be displayed in plain text in the IBM Spectrum Protect client trace file. IBM X-Force ID: 151968.","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 Spectrum Protect","id":"CVE-2018-1882","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in MQ","id":"CVE-2018-1883"},"packages":[],"prev":{"headline":"Information disclosure in Robotic Process Automation with Automation Anywhere","id":"CVE-2018-1878"},"products":["Spectrum Protect","Spectrum Protect for Space Management"],"published":"2019-04-08","related":[{"cvss_score":8.4,"headline":"IBM Spectrum Protect Backup-Archive Client privilege escalation","id":"CVE-2023-28956","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":7.4,"headline":"Privilege escalation in Spectrum Protect for Virtual Environments","id":"CVE-2021-20532","kev_date_added":null,"published":"2021-04-26"},{"cvss_score":6.2,"headline":"Memory corruption in Spectrum Protect","id":"CVE-2021-39048","kev_date_added":null,"published":"2021-12-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in Spectrum Protect","id":"CVE-2018-1853","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":5.1,"headline":"Information disclosure in Spectrum Protect","id":"CVE-2018-1787","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":4.4,"headline":"Race condition in Spectrum Protect Backup-Archive Client","id":"CVE-2019-4406","kev_date_added":null,"published":"2019-11-25"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["IBM"]},"summary":"Attackers with access to trace files can read node passwords in plain text in specific IBM Spectrum Protect configurations.","url":"https://insights.sbomify.com/CVE-2018-1882/"}