{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4129 is a low-severity vulnerability in IBM Spectrum Protect, published on 2 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-4129 and fix it if it is affected.\n\nWhat it is: CVE-2019-4129 is a low-severity vulnerability in IBM Spectrum Protect, published on 2 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-4129 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-2019-4129/ (Markdown: https://insights.sbomify.com/CVE-2019-4129/index.md)","id":"CVE-2019-4129","markdown":"https://insights.sbomify.com/CVE-2019-4129/index.md","name":"CVE-2019-4129","record":{"aliases":["GHSA-f39m-ggvf-jp22"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Spectrum Protect","requires_auth":"low_privilege","summary":"Remote attackers can obtain sensitive architecture details via stack traces in error messages from IBM Spectrum Protect Operations Center.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"spectrum_protect_operations_center","vendor":"ibm"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.0/UI:N/AV:N/AC:H/C:L/I:N/A:N/S:U/PR:L/RC:C/E:U/RL:O","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"IBM Spectrum Protect Operations Center 7.1 and 8.1 could allow a remote attacker to obtain sensitive information, caused by an error message containing a stack trace. By creating an error with a stack trace, an attacker could exploit this vulnerability to potentially obtain details on the Operations Center architecture. IBM X-Force ID: 158279.","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-2019-4129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in Cloud Pak System","id":"CVE-2019-4130"},"packages":[],"prev":{"headline":"Cross-site scripting in Cloud Private","id":"CVE-2019-4120"},"products":["Spectrum Protect"],"published":"2019-07-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in Spectrum Protect","id":"CVE-2019-4087","kev_date_added":null,"published":"2019-07-02"},{"cvss_score":9.1,"headline":"Code injection in Spectrum Protect Operations Center","id":"CVE-2020-4693","kev_date_added":null,"published":"2020-09-02"},{"cvss_score":8,"headline":"File upload in Spectrum Protect Operations Center","id":"CVE-2020-4955","kev_date_added":null,"published":"2021-02-15"},{"cvss_score":7.4,"headline":"Privilege escalation in Spectrum Protect","id":"CVE-2019-4088","kev_date_added":null,"published":"2019-07-02"},{"cvss_score":5.9,"headline":"Auth bypass in Spectrum Protect Server","id":"CVE-2022-22485","kev_date_added":null,"published":"2022-06-17"},{"cvss_score":5.3,"headline":"Auth bypass in Spectrum Protect Operations Center","id":"CVE-2020-4771","kev_date_added":null,"published":"2020-11-23"},{"cvss_score":5.1,"headline":"Information disclosure in Spectrum Protect Operations Center","id":"CVE-2021-38901","kev_date_added":null,"published":"2021-12-13"}],"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-16","vendors":["IBM"]},"summary":"Remote attackers can obtain sensitive architecture details via stack traces in error messages from IBM Spectrum Protect Operations Center.","url":"https://insights.sbomify.com/CVE-2019-4129/"}