{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-1890 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-1890 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-1890 is a low-severity vulnerability in n/a, published on 6 Apr 2015. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-1890 and fix it if it is affected.\n\nWhat it is: CVE-2015-1890 is a low-severity vulnerability in n/a, published on 6 Apr 2015. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-1890 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-2015-1890/ (Markdown: https://insights.sbomify.com/CVE-2015-1890/index.md)","id":"CVE-2015-1890","markdown":"https://insights.sbomify.com/CVE-2015-1890/index.md","name":"CVE-2015-1890","record":{"aliases":["GHSA-8w4f-3765-r94w"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM GPFS","requires_auth":"unknown","summary":"Remote attackers can obtain sensitive cleartext keys from GPFS support archives due to lack of warning, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"general_parallel_file_system","vendor":"ibm"}],"cvss":{"score":3.5,"severity":"low","source":"nvd","vector":"AV:N/AC:M/Au:S/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"/usr/lpp/mmfs/bin/gpfs.snap in IBM General Parallel File System (GPFS) 4.1 before 4.1.0.7 produces an archive potentially containing cleartext keys, and lacks a warning about reviewing this archive to detect included keys, which might allow remote attackers to obtain sensitive information by leveraging access to a technical-support data stream.","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-2015-1890","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-1892"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2015-1889"},"products":["n/a"],"published":"2015-04-06","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2015-0198","kev_date_added":null,"published":"2015-03-24"},{"cvss_score":7.4,"headline":"Privilege escalation in Spectrum Scale","id":"CVE-2018-1431","kev_date_added":null,"published":"2018-06-13"},{"cvss_score":7.2,"headline":"Memory corruption in Spectrum Scale","id":"CVE-2016-6115","kev_date_added":null,"published":"2017-02-01"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2015-4974","kev_date_added":null,"published":"2015-10-26"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2015-0197","kev_date_added":null,"published":"2015-03-24"},{"cvss_score":7,"headline":"Privilege escalation in n/a","id":"CVE-2016-2984","kev_date_added":null,"published":"2016-11-25"},{"cvss_score":7,"headline":"Privilege escalation in n/a","id":"CVE-2016-2985","kev_date_added":null,"published":"2016-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-08-06","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive cleartext keys from GPFS support archives due to lack of warning, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2015-1890/"}