Skip links

Memory Corruption vulnerability in SAP NetWeaver Instance Agent Service, SAP security note 2509284

Description

SAP startservice allows an attacker to leverage logical errors in memory management to cause a memory corruption.

Some well-known impacts of Memory Corruption vulnerability are –

  • system information disclosure or system crash in worst cases
  • vulnerability might have direct impact on confidentiality, integrity and availability of a system
  • information gathered can be used to craft further attacks, possibly with more severe consequences

CVSS Information

CVSS v3 Base Score: 6.6 / 10
CVSS v3 Base Vector:

AV : Attack Vector (Related exploit range)

Network (N)

AC : Attack Complexity (Required attack complexity)

High (H)

PR : Privileges Required (Level of privileges needed to exploit)

High (H)

UI : User Interaction (Required user participation)

None (N)

S : Scope (Change in scope due to impact caused to components beyond the vulnerable component)

Unchanged (U)

C : Impact to Confidentiality

High (H)

I : Impact to Integrity

High (H)

A : Impact to Availability

High (H)

SAP provides this CVSS v3 base score as an estimate of the risk posed by the issue reported in this note. This estimate does not take into account your own system configuration or operational environment. It is not intended to replace any risk assessments you are advised to conduct when deciding on the applicability or priority of this SAP security note. For more information, see the FAQ section at https://support.sap.com/securitynotes.

Available fix and Supported packages

  • KRNL64UC | 7.53 | 7.53
  • KERNEL | 7.52 | 7.52
  • KERNEL | 7.53 | 7.53
  • SAP KERNEL 7.52 64-BIT UNICODE | SP024 | 000024
  • SAP KERNEL 7.53 64-BIT | SP014 | 000014
  • SAP KERNEL 7.53 64-BIT UNICODE | SP014 | 000014

Affected component

    BC-CST-STS
    Startup Service

CVSS

Score: 0

Exploit

Exploit is not available.
For detailed information please contact the mail [email protected]

URL

https://launchpad.support.sap.com/#/notes/2509284

TAGS

#Buffer-overflow
#heap-overflow