SAP S-4HANA 104/105/106/107 Manage Journal Entry Template denial of service

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in SAP S-4HANA 104/105/106/107. Impacted is an unknown function of the component Manage Journal Entry Template. This manipulation causes denial of service. This vulnerability is handled as CVE-2023-35870. The attack can be initiated remotely. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in SAP S-4HANA 104/105/106/107 and classified as problematic. Affected by this vulnerability is some unknown processing of the component Manage Journal Entry Template. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect integrity, and availability. The summary by CVE is:
When creating a journal entry template in SAP S/4HANA (Manage Journal Entry Template) - versions S4CORE 104, 105, 106, 107, an attacker could intercept the save request and change the template, leading to an impact on confidentiality and integrity of the resource. Furthermore, a standard template could be deleted, hence making the resource temporarily unavailable.
The weakness was released 07/11/2023. It is possible to read the advisory at me.sap.com. This vulnerability is known as CVE-2023-35870 since 06/19/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
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: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.3
NVD Vector: 🔍
CNA Base Score: 6.3
CNA Vector (SAP SE): 🔍
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: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
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: 🔍
0-Day Time: 🔍
Timeline
06/19/2023 🔍07/11/2023 🔍
07/11/2023 🔍
07/27/2023 🔍
Sources
Vendor: sap.comAdvisory: me.sap.com
Status: Confirmed
CVE: CVE-2023-35870 (🔍)
GCVE (CVE): GCVE-0-2023-35870
GCVE (VulDB): GCVE-100-233491
scip Labs: https://www.scip.ch/en/?labs.20150716
Entry
Created: 07/11/2023 07:24Updated: 07/27/2023 14:37
Changes: 07/11/2023 07:24 (48), 07/18/2023 13:03 (1), 07/27/2023 14:37 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Can You explain me why did You use cpe "sap:s-4hana" instead of NVD Nist official cpes "sap:hana" OR "sap:s\/4hana" ?
Could You update ?
Best Regards,
TEAM CERT
We would be very grateful.
Best Regards,
TEAM CERT
Best Regards,
TEAM CERT
Do you want to use VulDB in your project?
Use the official API to access entries easily!