{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4377 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4377 is a medium-severity vulnerability in Ibm Sterling B2b Integrator, published on 25 Jun 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-4377 and fix it if it is affected.\n\nWhat it is: CVE-2019-4377 is a medium-severity vulnerability in Ibm Sterling B2b Integrator, published on 25 Jun 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-4377 in the wild and no public exploit code.\n\nAffected product: Ibm Sterling B2b Integrator. 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-4377/ (Markdown: https://insights.sbomify.com/CVE-2019-4377/index.md)","id":"CVE-2019-4377","markdown":"https://insights.sbomify.com/CVE-2019-4377/index.md","name":"CVE-2019-4377","record":{"aliases":["GHSA-x9r7-5c46-9x5p"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"B2B integration server","requires_auth":"low_privilege","summary":"Attackers can obtain sensitive system information from stack traces in IBM Sterling B2B Integrator to facilitate further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_b2b_integrator","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/I:N/AV:N/C:L/S:U/A:N/PR:L/UI:N/AC:L/RC:C/E:U/RL:O","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"IBM Sterling B2B Integrator 6.0.0.0 and 6.0.0.1 reveals sensitive information from a stack trace that could be used in further attacks against the system. IBM X-Force ID: 162803.","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 Sterling B2B Integrator","id":"CVE-2019-4377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:sterling_b2b_integrator","products":["ibm:sterling_b2b_integrator"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in MQ","id":"CVE-2019-4378"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-4369"},"products":["Sterling B2B Integrator"],"published":"2019-06-25","related":[{"cvss_score":9.8,"headline":"IBM WebSphere Application Server and Server Hypervisor Edition Code Injection.","id":"CVE-2015-7450","kev_date_added":"2022-01-10","published":"2016-01-02"},{"cvss_score":8.8,"headline":"IBM Sterling B2B Integrator Standard Edition code execution","id":"CVE-2024-31903","kev_date_added":null,"published":"2025-01-22"},{"cvss_score":8.8,"headline":"Deserialization in Sterling B2B Integrator","id":"CVE-2019-4728","kev_date_added":null,"published":"2021-01-05"},{"cvss_score":8.8,"headline":"Privilege escalation in Sterling B2B Integrator","id":"CVE-2020-4762","kev_date_added":null,"published":"2021-01-05"},{"cvss_score":8.8,"headline":"SQL injection in Sterling B2B Integrator","id":"CVE-2017-1174","kev_date_added":null,"published":"2017-08-10"},{"cvss_score":8.8,"headline":"SQL injection in Sterling B2B Integrator","id":"CVE-2017-1347","kev_date_added":null,"published":"2017-06-23"},{"cvss_score":8.2,"headline":"XML external entity in Sterling B2B Integrator","id":"CVE-2017-1192","kev_date_added":null,"published":"2017-08-10"}],"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 can obtain sensitive system information from stack traces in IBM Sterling B2B Integrator to facilitate further attacks.","url":"https://insights.sbomify.com/CVE-2019-4377/"}