CVE-2019-4461
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM Cloud Orchestrator versions 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. Attackers can inject malicious headers into HTTP responses through cache manipulation, enabling Web Cache poisoning, XSS attacks, and potentially sensitive information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.4.0.0, <= 2.4.0.5>= 2.5.0.0, <= 2.5.0.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Cloud Orchestrator installationLocate the IBM Cloud Orchestrator installation directory and check for version information files, typically found in the product's installation root or version manifestAffected if IBM Cloud Orchestrator is not installed on the system
-
Determine installed versionRead the version file or execute the product version command specific to IBM Cloud Orchestrator to obtain the exact version number (e.g., 2.4.0.x or 2.5.0.x)Affected if The installed version falls within 2.4.0.0 through 2.4.0.5 or 2.5.0.0 through 2.5.0.9
-
Verify HTTP caching is enabledExamine the IBM Cloud Orchestrator configuration files for HTTP caching settings, typically in web server or proxy configuration files within the product directoryAffected if HTTP caching is enabled and the product version is within the affected ranges listed above
-
Inspect cache control headersReview the HTTP response headers generated by IBM Cloud Orchestrator for proper cache-control and header sanitization configurationsAffected if Cache-control headers are missing, improperly configured, or the application does not sanitize user input in cache-related headers
You are affected if IBM Cloud Orchestrator versions 2.4.0.0 through 2.4.0.5 or 2.5.0.0 through 2.5.0.9 are installed with HTTP caching enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches for IBM Cloud Orchestrator (versions beyond 2.4.0.5 for the 2.4 branch and beyond 2.5.0.9 for the 2.5 branch) and configure proper HTTP cache headers to prevent response splitting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-4461 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data