SAP NetWeaver 7.40 SP12 PREPARE_CHECK_CAPACITY access control

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in SAP NetWeaver 7.40 SP12. This impacts the function PREPARE_CHECK_CAPACITY. Performing a manipulation results in access control.
This vulnerability is identified as CVE-2016-7435. The attack can be initiated remotely. There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in SAP NetWeaver 7.40 SP12 (Solution Stack Software). This affects the function PREPARE_CHECK_CAPACITY. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 10/11/2016 by Pablo Artuso with Onapsis as ONAPSIS-2016-044 as confirmed mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The public release was coordinated with SAP. This vulnerability is uniquely identified as CVE-2016-7435 since 09/09/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 251 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93272†). Entries connected to this vulnerability are available at VDB-92291, VDB-92293, VDB-92294 and VDB-92542. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.sap.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 8.9
VulDB Base Score: 9.1
VulDB Temp Score: 8.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
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: Access controlCWE: CWE-264
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Timeline
11/26/2015 🔍11/27/2015 🔍
08/03/2016 🔍
09/09/2016 🔍
10/03/2016 🔍
10/05/2016 🔍
10/11/2016 🔍
10/12/2016 🔍
09/22/2022 🔍
Sources
Vendor: sap.comAdvisory: ONAPSIS-2016-044
Researcher: Pablo Artuso
Organization: Onapsis
Status: Confirmed
Coordinated: 🔍
CVE: CVE-2016-7435 (🔍)
GCVE (CVE): GCVE-0-2016-7435
GCVE (VulDB): GCVE-100-92541
SecurityFocus: 93272 - SAP Netweaver CVE-2016-7435 Multiple OS Command Injection Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150716
See also: 🔍
Entry
Created: 10/12/2016 09:51Updated: 09/22/2022 18:23
Changes: 10/12/2016 09:51 (59), 05/07/2019 16:34 (14), 09/22/2022 18:23 (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.