Code Injection vulnerability in SAP S/4HANA (Manage Substitution/Validation Rules)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SAP_SE | SAP S/4HANA (Manage Substitution/Validation Rules) | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sap Se | Sap S/4hana (manage Substitution/validation Rules) |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.481% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sap Se
Sap Se sap S/4hana (manage Substitution/validation Rules) |
|
| Vendors & Products |
Sap Se
Sap Se sap S/4hana (manage Substitution/validation Rules) |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SAP S/4HANA (Manage Substitution/Validation Rules) does not sufficiently validate input processed by rule definition functionality that utilizes a domain-specific scripting language. An authenticated attacker with specific business privileges could submit specially crafted input, which is interpreted as executable ABAP code by the rule processing logic. Successful exploitation could allow the attacker to execute ABAP arbitrary code into the system, resulting in full compromise of the affected system and high impact on confidentiality, integrity, and availability of the system. | |
| Title | Code Injection vulnerability in SAP S/4HANA (Manage Substitution/Validation Rules) | |
| Weaknesses | CWE-94 | |
| References |
| |
| Metrics |
cvssV3_1
|