IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise 2.5 through 2.5.0.9 and 2.4 through 2.4.0.5 could allow a local user to obtain
IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise 2.5 through 2.5.0.9 and 2.4 through 2.4.0.5 could allow a local user to obtain sensitive information from SessionManagement cookies. IBM X-Force ID: 162259.
- Published
- Oct 24, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-552
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
13
Monitor
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 3.3
- CNA · ibm
- 4.0
- 0.7 point gap
CVSS:3.0/I:N/AV:L/A:N/C:L/S:U/PR:N/AC:L/UI:N/RL:O/RC:C/E:U
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | cloud orchestrator | cpe:2.3:a:ibm:cloud_orchestrator |
| ibm | cloud orchestrator enterprise | cpe:2.3:a:ibm:cloud_orchestrator_enterprise |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm cloud orchestrator2.4 and later · up to 2.4.0.5 inclusive
- ibm cloud orchestrator2.5 and later · up to 2.5.0.9 inclusive
- ibm cloud orchestrator enterprise2.4 and later · up to 2.4.0.5 inclusive
- ibm cloud orchestrator enterprise2.5 and later · up to 2.5.0.9 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
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 … (+4)affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-4399IBM Cloud Orchestrator 2.4 through 2.4.0.5 and 2.5 through 2.5.0.9 uses weaker than expected cryptographic algorithms that could allow an at30Monitor
- CVE-2016-0204Open redirect vulnerability in IBM Cloud Orchestrator 2.4.x before 2.4.0 FP3 allows remote authenticated users to redirect users to arbitrar27Monitor
- CVE-2019-4397IBM 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 URL26Monitor
- CVE-2016-0203A vulnerability has been identified in the IBM Cloud Orchestrator task API.22Monitor
- CVE-2019-4461IBM 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 co21Monitor
- CVE-2019-4396IBM 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 vali21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-552 · Files or Directories Accessible to External PartiesCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- OS Credential DumpingT1003
- Data from Network Shared DriveT1039
- Automated CollectionT1119
- Data from Information RepositoriesT1213
- Data from Cloud Storage ObjectT1530
- Unsecured Credentials: Credentials in FilesT1552.001
- Unsecured Credentials: Bash HistoryT1552.003
- Unsecured Credentials: Private KeysT1552.004
- Unsecured Credentials: Group Policy PreferencesT1552.006
- Credentials from Password StoresT1555
- Data from Configuration RepositoryT1602
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.