dbcve.org
NetweaverApplication · Sap

CVE-2016-7435

CRITICAL · 9.1 CVSS v3.0 Published 2016-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The (1) SCTC_REFRESH_EXPORT_TAB_COMP, (2) SCTC_REFRESH_CHECK_ENV, and (3) SCTC_TMS_MAINTAIN_ALOG functions in the SCTC subpackage in SAP Netweaver 7.40 SP 12 allow remote authenticated users with certain permissions to execute arbitrary commands via vectors involving a CALL 'SYSTEM' statement, aka SAP Security Note 2260344.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated command injection in SAP NetWeaver 7.40 SP12 where the SCTC subpackage functions (SCTC_REFRESH_EXPORT_TAB_COMP, SCTC_REFRESH_CHECK_ENV, SCTC_TMS_MAINTAIN_ALOG) use the ABAP CALL 'SYSTEM' statement to execute OS commands without proper input validation, allowing remote authenticated attackers to execute arbitrary commands on the underlying operating system.

MitigationApply SAP Security Note 2260344 immediately. Revoke permissions from unauthorized users to the SCTC functions and implement input validation on any user-supplied parameters before passing to system calls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NetweaverApplication
Affected:= 7.40

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify SAP NetWeaver version
    Check the SAP system version using transaction SM37 or by viewing system information in SAP GUI. Confirm the NetWeaver version is 7.40.
    Affected if The installed version is SAP NetWeaver 7.40
  2. Check Support Package level
    Using SAP transaction SPAM or SAINT, check the Support Package level for the SAP_BASIS component. Confirm if SP12 is applied.
    Affected if Support Package 12 (SP12) for SAP NetWeaver 7.40 is installed
  3. Identify SCTC function modules
    Using SAP transaction SE37 (Function Builder), search for function modules: SCTC_REFRESH_EXPORT_TAB_COMP, SCTC_REFRESH_CHECK_ENV, and SCTC_TMS_MAINTAIN_ALOG. Check if these exist in the system.
    Affected if Any of these three SCTC function modules exist in the system
  4. Check function module authorization
    Using transaction SU53 or by reviewing role permissions in PFCG, determine which users or roles have authorization to execute the SCTC function modules.
    Affected if Users beyond system administrators have execution authorization to the SCTC functions
  5. Review ABAP code for CALL SYSTEM statement
    Using transaction SE37, display the source code of the SCTC function modules. Look for the ABAP statement CALL 'SYSTEM' being used to execute OS commands.
    Affected if The SCTC functions contain CALL 'SYSTEM' statements without proper input validation

If running SAP NetWeaver 7.40 with SP12 applied and the SCTC function modules are present and accessible to authenticated users, the system is vulnerable to command injection via the CALL SYSTEM statement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP Security Note 2260344 immediately. Revoke permissions from unauthorized users to the SCTC functions and implement input validation on any user-supplied parameters before passing to system calls.

Recommended fix Moderate confidence

SAP NetWeaver 7.40 SP 13 or later

  1. Apply SAP Security Note 2260344, or upgrade SAP Netweaver 7.40 to a patched Support Package (SP 13 or later)
  2. After applying the patch or upgrade, verify the SCTC functions no longer accept arbitrary command input via CALL 'SYSTEM'
  3. Review user permissions for the SCTC subpackage and restrict to only necessary authorized users
  4. Test the fix in a non-production environment before deploying to production
Caveat Standard SAP Support Package stack upgrades require regression testing; ensure custom ABAP code does not depend on the vulnerable function behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-7435 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data