Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2019-4396

IBM Cloud Orchestrator 2.4 through 2.4.0.5 and 2.5 through 2.5.0.9 is vulnerable to HTTP response splitting attacks, caused by improper…

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 attacks, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information. IBM X-Force ID: 162236.

Timeline

  1. ID reserved

    By ibm

  2. · 10 months later

    Published

  3. · 5 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2019-4396, by who scored it
Scored byCVSSScoreVector
ibmCNA (assigner)3.0Medium5.4CVSS:3.0/AV:N/AC:L/I:L/PR:L/A:N/UI:R/C:L/S:C/RC:C/E:U/RL:O
NVDNVD · Modified3.1Medium5.4CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.67% · top 48% of all CVEs (10 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.

Affected products

  • IBM · Cloud Orchestrator

    • affected 2.4
    • affected 2.4.0.1
    • affected 2.4.0.2
    • affected 2.5
    • affected 2.5.0.1
    • affected 2.4.0.3
    • affected 2.5.0.2
    • affected 2.4.0.4
    • affected 2.5.0.3
    • affected 2.5.0.4
    • affected 2.4.0.5
    • affected 2.5.0.5
    • affected 2.5.0.6
    • affected 2.5.0.7
    • affected 2.5.0.8
    • affected 2.5.0.9

References

2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2019-4396 badge
[![CVE-2019-4396](https://cveledger.app/badge/CVE-2019-4396.svg)](https://cveledger.app/cve/CVE-2019-4396)

Record last updated .