CVE-2021-44235
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 · uneditedTwo methods of a utility class in SAP NetWeaver AS ABAP - versions 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 753, 754, 755, 756, allow an attacker with high privileges and has direct access to SAP System, to inject code when executing with a certain transaction class builder. This could allow execution of arbitrary commands on the operating system, that could highly impact the Confidentiality, Integrity and Availability of the system.
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 confidenceA code injection vulnerability exists in SAP NetWeaver AS ABAP versions 700-756 where two methods of a utility class allow an attacker with high privileges and direct system access to inject arbitrary code when executing through a specific transaction class builder, leading to OS command execution with high impact on system confidentiality, integrity, and availability.
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= 700= 701= 702= 710= 711= 730= 731= 740= 750= 751= 752= 753CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP NetWeaver AS ABAP versionCheck the installed ABAP version using transaction code SM51 or the System -> Status menu in SAP GUI. Compare the version number to the affected list: 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 753.Affected if The installed version matches any of these specific versions (700-753 range).
-
Identify privileged users with accessUse transaction SU01 or SUIM to review user accounts that have high privileges and access to the transaction class builder functionality.Affected if Multiple user accounts have high privilege levels and direct system access to the class builder transactions.
-
Audit transaction class builder usageReview system logs and trace files (transaction ST03N, STAT, or SAAB) for execution history of the specific transaction class builder that triggers the vulnerable utility class methods.Affected if Execution logs show activity through the transaction class builder that invokes the two vulnerable methods.
-
Inspect the vulnerable utility classExamine the ABAP code of the utility class containing the two methods referenced in this vulnerability using transaction SE80 or SE24, if accessible.Affected if The utility class is present and contains the two methods susceptible to code injection.
A system is affected if it runs a listed ABAP version (700-753) AND has users with high privileges able to access and execute the transaction class builder that triggers the vulnerable utility class methods.
Generated from the published advisory. Verify against your own configuration.
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 dataApply relevant SAP security notes/patches for this vulnerability and restrict access to the affected transaction class builder functionality to only essential, authorized personnel.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-44235 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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