{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4461 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4461 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4461 is a medium-severity vulnerability in IBM Cloud Orchestrator, published on 25 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-4461 and fix it if it is affected.\n\nWhat it is: CVE-2019-4461 is a medium-severity vulnerability in IBM Cloud Orchestrator, published on 25 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-4461 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-4461/ (Markdown: https://insights.sbomify.com/CVE-2019-4461/index.md)","id":"CVE-2019-4461","markdown":"https://insights.sbomify.com/CVE-2019-4461/index.md","name":"CVE-2019-4461","record":{"aliases":["GHSA-rvg7-hqxx-gj93"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Cloud Orchestrator","requires_auth":"low_privilege","summary":"Attackers can exploit HTTP Response Splitting in IBM Cloud Orchestrator to poison caches, execute XSS, and potentially access sensitive information.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"cloud_orchestrator","vendor":"ibm"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/I:L/PR:L/S:C/C:L/A:N/UI:R/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"IBM Cloud Orchestrator 2.4 through 2.4.0.5 and 2.5 through 2.5.0.9 is vulnerable to HTTP Response Splitting caused by improper caching of content. This would allow the attacker to perform further attacks, such as Web Cache poisoning, cross-site scripting and possibly obtain sensitive information. IBM X-Force ID: 163682.","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":"Other in Cloud Orchestrator","id":"CVE-2019-4461","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Cloud Pak System","id":"CVE-2019-4465"},"packages":[],"prev":{"headline":"Path traversal in API Connect","id":"CVE-2019-4460"},"products":["Cloud Orchestrator"],"published":"2019-10-25","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":"Cross-site scripting in Cloud Orchestrator","id":"CVE-2019-4459","kev_date_added":null,"published":"2019-10-24"},{"cvss_score":5.3,"headline":"Information disclosure in Cloud Orchestrator","id":"CVE-2019-4397","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 exploit HTTP Response Splitting in IBM Cloud Orchestrator to poison caches, execute XSS, and potentially access sensitive information.","url":"https://insights.sbomify.com/CVE-2019-4461/"}