dbcve.org
NetweaverApplication · Sap

CVE-2016-10311

CRITICAL · 9.8 CVSS v3.0 Published 2017-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Stack-based buffer overflow in SAP NetWeaver 7.0 through 7.5 allows remote attackers to cause a denial of service () by sending a crafted packet to the SAPSTARTSRV port, aka SAP Security Note 2295238.

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

Stack-based buffer overflow in SAP NetWeaver 7.0-7.5 allows remote attackers to cause denial of service via crafted packets sent to the SAPSTARTSRV port. The critical CVSS score of 9.8 indicates the vulnerability is remotely exploitable without authentication and likely has a low attack complexity.

MitigationApply SAP Security Note 2295238 which provides the vendor patch. As an interim measure, restrict network access to the SAPSTARTSRV port using firewall rules or network segmentation until the patch can be deployed.

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.0= 7.3= 7.4= 7.5

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify SAP NetWeaver installation and version
    Query the SAP system for its NetWeaver version using transaction code SM51 or by checking the SAP system info via SAP Management Console. Alternatively, examine the sapcvs file in the /usr/sap/<SID>/SYS/profile/ directory or use the SAP Version NWRFC SDK to programmatically query the version.
    Affected if The installed version is 7.0, 7.3, 7.4, or 7.5 exactly as listed in the affected versions.
  2. Determine if SAPSTARTSRV service is running and exposed
    Check if the SAPSTARTSRV process is running on the SAP system using operating system commands like ps aux | grep SAPSTARTSRV or by querying the SAP kernel processes. Verify if the port (typically 5xx13, where xx is the instance number) is listening and accessible from the network.
    Affected if SAPSTARTSRV is actively running and listening on a network-accessible port.
  3. Verify network exposure of SAPSTARTSRV port
    Use network scanning tools such as nmap to check if the SAPSTARTSRV port is exposed to untrusted networks, or review firewall rules and network configurations to determine if the port is reachable from outside the protected network segment.
    Affected if The SAPSTARTSRV port is reachable from network segments that include untrusted or external hosts.
  4. Confirm vulnerability applicability
    Review the installed SAP NetWeaver version against the affected version list (7.0, 7.3, 7.4, 7.5). If the version matches exactly, the environment contains the vulnerable configuration and is susceptible to the buffer overflow when SAPSTARTSRV is network-accessible.
    Affected if The environment runs any of the exact versions 7.0, 7.3, 7.4, or 7.5 AND has SAPSTARTSRV network-accessible.

The environment is affected if SAP NetWeaver version 7.0, 7.3, 7.4, or 7.5 is installed AND the SAPSTARTSRV service is running and network-accessible, allowing remote attackers to send crafted packets to trigger the buffer overflow.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP Security Note 2295238 which provides the vendor patch. As an interim measure, restrict network access to the SAPSTARTSRV port using firewall rules or network segmentation until the patch can be deployed.

Fix this in Netweaver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10311 — 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-10311 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