dbcve.org
Netweaver AbapApplication · Sap

CVE-2021-40495

MEDIUM · 5.3 CVSS v3.1 Published 2021-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
There are multiple Denial-of Service vulnerabilities in SAP NetWeaver Application Server for ABAP and ABAP Platform - versions 740, 750, 751, 752, 753, 754, 755. An unauthorized attacker can use the public SICF service /sap/public/bc/abap to reduce the performance of SAP NetWeaver Application Server ABAP and ABAP Platform.

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

This CVE describes multiple Denial-of-Service vulnerabilities in SAP NetWeaver ABAP (versions 740-755) exploitable through the public SICF service /sap/public/bc/abap. An unauthenticated attacker can send requests to this publicly accessible service to cause performance degradation, impacting system availability. The vulnerability stems from the exposure of an internal ABAP service via the Internet Communication Manager (ICM) without proper access restrictions.

MitigationDeactivate the public SICF service /sap/public/bc/abap via transaction SICF or implement proper access restrictions/URL filtering at the network level to block unauthorized access to this endpoint.

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
Netweaver AbapApplication
Affected:= 740= 750= 751= 752= 753= 754= 755
Netweaver Application Server AbapApplication
Affected:= 740= 750= 751= 752= 753= 754= 755

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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 installed SAP NetWeaver ABAP version
    Execute transaction code SM51 or check system version via SAPMMC or the SAP System Information screen (System > Status). Look for the Release and Support Package levels.
    Affected if The installed version is 740, 750, 751, 752, 753, 754, or 755.
  2. Verify if SICF service /sap/public/bc/abap is active
    Execute transaction code SICF. Navigate to the path: default_host > sap > public > bc > abap. Check the Service Status column for the 'abap' service.
    Affected if The service status shows as 'active' (green indicator).
  3. Confirm service is externally accessible via ICM
    Execute transaction code SMICM (Internet Communication Manager). Go to Goto > Services and verify that HTTP/HTTPS ports are active. Then test accessing https://<host>/sap/public/bc/abap from a non-SAP network location.
    Affected if The ICM HTTP/HTTPS ports are active and the URL responds (even with an error or redirect), indicating the endpoint is reachable.
  4. Check if service requires authentication
    In transaction SICF, double-click the /sap/public/bc/abap service. Go to the Logon Data tab. Verify the Anonymous Logon setting and authentication method configured.
    Affected if Anonymous access is enabled or no authentication is required for this service.

A system is affected if it runs SAP NetWeaver ABAP versions 740-755 with the SICF service /sap/public/bc/abap active and externally accessible without authentication, allowing unauthenticated attackers to cause DoS via repeated requests.

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

Deactivate the public SICF service /sap/public/bc/abap via transaction SICF or implement proper access restrictions/URL filtering at the network level to block unauthorized access to this endpoint.

Fix this in Netweaver Abap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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