| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in SAP BusinessObjects BI Platform, BusinessObjects Edge and BusinessObjects XI. This affects an unknown function of the component GIOP Packet Handler. This manipulation causes memory corruption. This vulnerability appears as CVE-2015-7730. There is no available exploit.
Details
A vulnerability has been found in SAP BusinessObjects BI Platform, BusinessObjects Edge and BusinessObjects XI (affected version not known) and classified as problematic. Affected by this vulnerability is some unknown functionality of the component GIOP Packet Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. The summary by CVE is:
SAP BusinessObjects BI Platform 4.1, BusinessObjects Edge 4.0, and BusinessObjects XI (BOXI) 3.1 R3 allow remote attackers to cause a denial of service (out-of-bounds read and listener crash) via a crafted GIOP packet, aka SAP Security Note 2001108.
The weakness was presented 10/15/2015 as 2001108 as confirmed security note (Website). The advisory is shared at onapsis.com. This vulnerability is known as CVE-2015-7730 since 10/06/2015. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/22/2022).
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 databases at SecurityFocus (BID 76830†) and Vulnerability Center (SBV-54399†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.sap.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/22/2015 🔍10/06/2015 🔍
10/15/2015 🔍
10/15/2015 🔍
10/16/2015 🔍
11/15/2015 🔍
06/22/2022 🔍
Sources
Vendor: sap.comAdvisory: 2001108
Status: Confirmed
CVE: CVE-2015-7730 (🔍)
GCVE (CVE): GCVE-0-2015-7730
GCVE (VulDB): GCVE-100-78493
SecurityFocus: 76830
SecurityTracker: 1033637
Vulnerability Center: 54399 - SAP BusinessObjects BI Platform, Edge and XI Remote DoS via a Crafted GIOP Packet, Medium
scip Labs: https://www.scip.ch/en/?labs.20150716
Entry
Created: 10/16/2015 10:36Updated: 06/22/2022 02:01
Changes: 10/16/2015 10:36 (47), 04/12/2018 17:13 (7), 06/22/2022 02:01 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.

No comments yet. Languages: en.
Please log in to comment.