Skip links
Picture of Vahagn Vardanian

Vahagn Vardanian

Co-founder and CTO of RedRays

Code injection vulnerability in SV-SMG-SDD, SAP security note 1642810

SAP Note 1642810
SAP Security Note
Medium priority

SAP security note 1642810, “Code Injection Vulnerability in SV-SMG-SDD”, is a note released on 05.12.2012. Below are the symptom, SAP recommended solution and the affected software components.

ComponentService Data Download (SV-SMG-SDD)
PriorityCorrection with medium priority
TypeSAP Security Note
Version4
StatusReleased for Customer
Released on05.12.2012

Description

Symptom

This security note has been updated. For more detailed information, see Security Note 1727119.

Component SV-SMG-SDD contains code that permits the execution of arbitrary program code of the user’s choice. An attacker can therefore control the behavior of the system or potentially escalate privileges by executing malicious code without having legitimate credentials.

Solution

SAP_BASIS Releases 610 – 731

  • Implement the correction instructions provided in this note.

SAP_BASIS Releases 46B – 46D

  • If ST-PI Add-on is Installed: No further action is needed.
  • If ST-PI Add-on is Not Installed: Install the ST-PI add-on. Refer to Note 769623 or Note 1228898 for detailed installation instructions.

Reason and prerequisites

The program code allows the definition and execution of user-defined code that changes the system’s behavior. A valid and authenticated user is required with authorization to create and execute ABAP reports.

Depending on the code, the user can:

  • Inject and run their own code
  • Obtain additional information that should not be displayed
  • Modify or delete data
  • Modify the system’s output

References

Affected components

  • SAP_BASIS 46B to 46D
  • SAP_BASIS 610 to 640
  • SAP_BASIS 700 to 702
  • SAP_BASIS 710 to 730
  • SAP_BASIS 731

Full note on SAP: SAP Support Launchpad note 1642810

Detailed exploitation and proof-of-concept material for this note is maintained in the RedRays Security Platform. For access, contact [email protected].

Explore More