dbcve.org
Netweaver AbapApplication · Sap

CVE-2021-33677

HIGH · 7.5 CVSS v3.1 Published 2021-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
SAP NetWeaver ABAP Server and ABAP Platform, versions - 700, 702, 730, 731, 804, 740, 750, 784, expose functions to external which can lead to information disclosure.

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 · moderate confidence

SAP NetWeaver ABAP Server and ABAP Platform (versions 700, 702, 730, 731, 804, 740, 750, 784) expose callable functions to external entities, allowing unauthorized access that leads to information disclosure. This appears to be a vulnerability in function module exposure or RFC endpoint configuration.

MitigationApply relevant SAP Security Notes/patches for CVE-2021-33677 and review function module exposure settings to restrict external access to sensitive functions.

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:= 700= 702= 730= 731= 740= 750= 784= 804
Netweaver Application Server AbapApplication
Affected:= 700= 702= 730= 731= 740= 750= 784= 804

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

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

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 ABAP version
    Execute transaction code SM51 or use ABAP transaction code 'VERS' to display the SAP NetWeaver ABAP kernel and software component versions. Alternatively, check transaction SE03 or use SAPMSSY2 to view system version information.
    Affected if The installed version matches any of: 700, 702, 730, 731, 740, 750, 784, or 804.
  2. Review RFC destination configuration
    Execute transaction code SM59 to display RFC destinations. Inspect all TCP/IP and HTTP destinations configured for external access, particularly those with 'Registered Server Program' or 'TCP/IP' connection types.
    Affected if RFC destinations exist that permit external (non-internal network) connections without proper restriction.
  3. Check function module exposure settings
    Use transaction code SE37 (Function Builder) to examine function modules. Review transaction code SIFP (or examine table SIFPREG) to identify function modules registered for external access. Check transaction code SRTMNG for exposed web services.
    Affected if Sensitive function modules are exposed to external callers via RFC, RFC-enabled function modules, or web services without adequate authorization checks.
  4. Audit authorization role assignments for RFC
    Execute transaction code SUIM to query roles with authorization object S_RFC (RFC_TYPE, RFC_NAME, ACTVT). Review transaction code PFCG to examine roles granting broad RFC access to function groups such as RFC_METADATA or system function groups.
    Affected if Roles or users exist with excessive RFC authorization enabling access to sensitive function modules from external sources.

The environment is affected if the SAP NetWeaver ABAP version matches one of the listed affected versions (700, 702, 730, 731, 740, 750, 784, 804) AND function modules or RFC endpoints are configured to allow external access without proper restrictions.

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 relevant SAP Security Notes/patches for CVE-2021-33677 and review function module exposure settings to restrict external access to sensitive functions.

Fix this in Netweaver Abap 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-2021-33677 — 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-33677 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