Login Request a demo
Low severity · published Feb 8, 2017
CVE-2016-0202
A vulnerability has been identified in tasks, backend object generated for handling any action performed by the application in IBM Cloud Orchestrator
3.3
CVSS
0.3%
EPSS
No
On KEV
Description
A vulnerability has been identified in tasks, backend object generated for handling any action performed by the application in IBM Cloud Orchestrator. It is possible for an authenticated user to view any task of the current users domain.
CVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 27% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CO
Cloud Orchestrator · Ibm
2.3; 2.3.0.1; 2.4; 2.4.0.1; 2.4.0.2; 2.4.0.3 · source: NVD
Affected product
CO
Cloud Orchestrator
Ibm
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-0202
CVE.org
https://www.cve.org/CVERecord?id=CVE-2016-0202
Patch
http://www.ibm.com/support/docview.wss?uid=swg2C1000134
Third Party Advisory
http://www.securityfocus.com/bid/94578
More from Cloud Orchestrator
7.5
CVE-2019-4399
IBM 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 attacker to decrypt highly sensitive…
6.8
CVE-2016-0204
Open redirect vulnerability in IBM Cloud Orchestrator 2.4.x before 2.4.0 FP3 allows remote authenticated users to redirect users to arbitrary web sites and conduct phishing…
6.5
CVE-2019-4397
IBM 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 URL parameters
5.5
CVE-2016-0203
A vulnerability has been identified in the IBM Cloud Orchestrator task API
5.4
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 content