{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-4397 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4397 is a medium-severity vulnerability in IBM Cloud Orchestrator, published on 24 Oct 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-4397 and fix it if it is affected.\n\nWhat it is: CVE-2019-4397 is a medium-severity vulnerability in IBM Cloud Orchestrator, published on 24 Oct 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-4397 in the wild and no public exploit code.\n\nAffected product: IBM Cloud Orchestrator. 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-4397/ (Markdown: https://insights.sbomify.com/CVE-2019-4397/index.md)","id":"CVE-2019-4397","markdown":"https://insights.sbomify.com/CVE-2019-4397/index.md","name":"CVE-2019-4397","record":{"aliases":["GHSA-fv6q-cpfx-7rj8"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Cloud Orchestrator","requires_auth":"low_privilege","summary":"Attackers can access sensitive information stored in URL parameters via logs or history, leading to data disclosure in IBM Cloud Orchestrator.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"cloud_orchestrator","vendor":"ibm"},{"product":"cloud_orchestrator_enterprise","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AC:H/UI:N/S:U/PR:L/C:H/A:N/I:N/AV:N/RL:O/RC:C/E:U","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise 2.5 through 2.5.0.9 and 2.4 through 2.4.0.5 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 162239","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 Cloud Orchestrator","id":"CVE-2019-4397","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":"Information disclosure in Cloud Orchestrator","id":"CVE-2019-4398"},"packages":[],"prev":{"headline":"Other in Cloud Orchestrator","id":"CVE-2019-4396"},"products":["Cloud Orchestrator"],"published":"2019-10-24","related":[{"cvss_score":6.8,"headline":"Open redirect in n/a","id":"CVE-2016-0204","kev_date_added":null,"published":"2016-10-16"},{"cvss_score":5.9,"headline":"Weak cryptography in Cloud Orchestrator","id":"CVE-2019-4399","kev_date_added":null,"published":"2019-10-25"},{"cvss_score":5.5,"headline":"Information disclosure in Cloud Orchestrator","id":"CVE-2016-0203","kev_date_added":null,"published":"2017-02-08"},{"cvss_score":5.4,"headline":"Other in Cloud Orchestrator","id":"CVE-2019-4396","kev_date_added":null,"published":"2019-10-25"},{"cvss_score":5.4,"headline":"Other in Cloud Orchestrator","id":"CVE-2019-4461","kev_date_added":null,"published":"2019-10-25"},{"cvss_score":5.4,"headline":"Cross-site scripting in Cloud Orchestrator","id":"CVE-2019-4459","kev_date_added":null,"published":"2019-10-24"}],"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 access sensitive information stored in URL parameters via logs or history, leading to data disclosure in IBM Cloud Orchestrator.","url":"https://insights.sbomify.com/CVE-2019-4397/"}