CVE-2019-0328
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 · uneditedABAP Tests Modules (SAP Basis, versions 7.0, 7.1, 7.3, 7.31, 7.4, 7.5) of SAP NetWeaver Process Integration enables an attacker the execution of OS commands with privileged rights. An attacker could thereby impact the 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 confidenceOS command injection vulnerability in ABAP Test Modules of SAP Basis (NetWeaver Process Integration) allows execution of operating system commands with privileged rights. The vulnerability exists in the test functionality that interfaces with the OS layer without proper input sanitization.
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= 7.0= 7.1= 7.3= 7.4= 7.5= 7.31CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Identify SAP NetWeaver Process Integration versionExecute transaction code SM51 in SAP GUI to view the installed release version, or access SAP NetWeaver Administrator > System > Overview to confirm the NetWeaver version.Affected if The installed NetWeaver version is 7.0, 7.1, 7.3, 7.4, 7.5, or 7.31 as listed in the affected versions.
-
Locate ABAP Test Modules in the systemUse transaction SE80 (Object Navigator) and search for test-related function modules or classes within the SAP Basis component, or use transaction SE37 (Function Builder) and look for test function modules that interface with operating system commands.Affected if Test modules that provide OS-layer interfaces exist in the system and are accessible to users.
-
Verify access to test functions is not restrictedUse transaction SUIM (User Information System) to query which users have authorization for test-related transaction codes or function modules, or review the authorization profiles assigned to user accounts with access to the SAP system.Affected if Users other than authorized Basis administrators have access to the ABAP Test Modules that interface with the OS layer.
A system is affected if it runs a vulnerable NetWeaver PI version (7.0, 7.1, 7.3, 7.4, 7.5, or 7.31) and has ABAP Test Modules with OS-layer interfaces accessible to users beyond authorized Basis administrators.
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 SAP Security Note for CVE-2019-0328 to patch the ABAP Test Modules. Restrict access to test functions to authorized Basis administrators only and follow SAP's security guidance for system hardening.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0328 — 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-2019-0328 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