CVE-2019-0270
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 Server of SAP NetWeaver and ABAP Platform fail to perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. This has been corrected in the following versions: KRNL32NUC 7.21, 7.21EXT, 7.22, 7.22EXT, KRNL32UC 7.21, 7.21EXT, 7.22, 7.22EXT, KRNL64NUC 7.21, 7.21EXT, 7.22, 7.22EXT, 7.49, 7.74, KRNL64UC 7.21, 7.21EXT, 7.22, 7.22EXT, 7.49, 7.73, 7.74, 8.04, KERNEL 7.21, 7.45, 7.49, 7.53, 7.73, 7.74, 7.75, 8.04.
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 confidenceThis is a privilege escalation vulnerability in SAP NetWeaver ABAP Server where authenticated users can bypass authorization checks to gain elevated privileges beyond what their account should normally permit. The flaw allows an authenticated attacker to perform actions they are not authorized to perform.
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.15= 7.21= 7.22= 7.49= 7.53= 7.73= 7.74= 7.75= 8.04= 7.21= 7.21ext= 7.22= 7.22ext= 7.21= 7.21ext= 7.22= 7.22ext= 7.21= 7.21ext= 7.22= 7.22ext= 7.21= 7.21ext= 7.22= 7.22ext= 7.49= 7.73= 7.74= 8.04CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 installed SAP kernel versionExecute transaction SM51 or use the SAP kernel version check command (e.g., 'sapkernel -v' or check the 'kernel' directory in the SAP file system for the SAPEXE*.SAR file)Affected if The installed kernel version matches any of these exact versions: 7.15, 7.21, 7.22, 7.49, 7.53, 7.73, 7.74, 7.75, or 8.04 for the KERNEL platform; 7.21, 7.21ext, 7.22, or 7.22ext for Krnl32nuc/Krnl32uc/Krnl64nuc; 7.49, 7.73, 7.74, or 8.04 for Krnl64uc in addition to the earlier versions
-
Verify kernel component typeIdentify which specific SAP kernel component is in use (KRNL32NUC, KRNL32UC, KRNL64NUC, KRNL64UC, or general KERNEL) by examining the kernel patch information in transaction SM51 or checking the kernel executable attributesAffected if The identified kernel component matches one of the affected component families listed in the CVE and the version matches the affected versions for that component
-
Confirm ABAP server usageVerify that the system is running SAP NetWeaver ABAP Server by checking transaction SM37 or checking system type via transaction S004Affected if The system is confirmed to be SAP NetWeaver ABAP Server and the kernel version falls within the affected version ranges
The environment is affected if it runs SAP NetWeaver ABAP Server with a kernel version matching any of the specific versions listed in the CVE for KERNEL, KRNL32NUC, KRNL32UC, KRNL64NUC, or KRNL64UC components.
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 the corresponding SAP kernel patch listed for the affected version (KRNL32NUC, KRNL32UC, KRNL64NUC, KRNL64UC, or KERNEL) to remediate this authorization bypass. Prioritize patching in non-production environments first and test thoroughly due to the critical nature of kernel updates.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0270 — 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-0270 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