IBM Sterling Order Management 9.2/9.3/9.4/9.5 cross-site request forgery
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability has been found in IBM Sterling Order Management 9.2/9.3/9.4/9.5 (Business Process Management Software) and classified as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a cross site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. As an impact it is known to affect integrity. An attacker might be able force legitimate users to initiate unwanted actions within the web application. The summary by CVE is:
IBM Sterling Order Management 9.2 - 9.5 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM Reference #: 2000943.
The bug was discovered 03/27/2017. The weakness was shared 03/31/2017 (Website). It is possible to read the advisory at ibm.com. This vulnerability is known as CVE-2016-8917 since 10/25/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/01/2017). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97150).
CVSSv3VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Cross site request forgery
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
03/27/2017 +153 days 🔍
03/27/2017 +0 days 🔍
03/31/2017 +4 days 🔍
03/31/2017 +0 days 🔍
04/01/2017 +1 days 🔍
04/01/2017 +0 days 🔍
Status: Not defined
CVE: CVE-2016-8917 (🔍)
SecurityFocus: 97150 - IBM Sterling Selling and Fulfillment Foundation Cross Site Request Forgery Vulnerability
OSVDB: - CVE-2016-8917 - IBM - Sterling Order Management - Cross-Site Request Forgery Issue
EntryCreated: 04/01/2017 10:08 AM
Changes: (64) software_type software_vendor software_name software_version vulnerability_discoverydate vulnerability_cwe vulnerability_risk vulnerability_cvss2_vuldb_basescore vulnerability_cvss2_vuldb_tempscore vulnerability_cvss2_vuldb_av vulnerability_cvss2_vuldb_ac vulnerability_cvss2_vuldb_au vulnerability_cvss2_vuldb_ci vulnerability_cvss2_vuldb_ii vulnerability_cvss2_vuldb_ai vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss3_vuldb_basescore vulnerability_cvss3_vuldb_tempscore vulnerability_cvss3_vuldb_av vulnerability_cvss3_vuldb_ac vulnerability_cvss3_vuldb_pr vulnerability_cvss3_vuldb_ui vulnerability_cvss3_vuldb_s vulnerability_cvss3_vuldb_c vulnerability_cvss3_vuldb_i vulnerability_cvss3_vuldb_a vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a advisory_date advisory_url advisory_confirm_url exploit_price_0day exploit_price_trend source_cve source_cve_assigned source_cve_nvd_published source_cve_nvd_summary source_osvdb_title source_securityfocus source_securityfocus_date source_securityfocus_class source_securityfocus_title advisory_location vulnerability_cvss2_vuldb_e vulnerability_cvss2_vuldb_rl vulnerability_cvss2_vuldb_rc vulnerability_cvss3_vuldb_e vulnerability_cvss3_vuldb_rl vulnerability_cvss3_vuldb_rc exploit_0day_days vulnerability_cvss3_nvd_basescore
Do you want to use VulDB in your project?
Use the official API to access entries easily!