CVE-2019-0349
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 · uneditedSAP Kernel (ABAP Debugger), 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, KRNL64UC 7.21, 7.21EXT, 7.22, 7.22EXT, 7.49, 7.73, KERNEL 7.21, 7.49, 7.53, 7.73, 7.75, 7.76, 7.77, allows a user to execute “Go to statement” without possessing the authorization S_DEVELOP DEBUG 02, resulting in Missing Authorization Check
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 missing authorization vulnerability in SAP's ABAP Debugger Kernel where users can execute the 'Go to statement' function without possessing the required S_DEVELOP DEBUG 02 authorization. This allows unauthorized users to bypass debug authorization controls and potentially access sensitive debugging functionality.
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.21= 7.21ext= 7.22= 7.22ext= 7.49= 7.53= 7.73= 7.75= 7.76= 7.77CVSS 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.
-
Check SAP Kernel versionExecute transaction SM51 or use the SAP kernel version check command to identify the installed kernel release and patch level. Compare this version against the affected list: 7.21, 7.21ext, 7.22, 7.22ext, 7.49, 7.53, 7.73, 7.75, 7.76, or 7.77.Affected if The installed kernel version matches one of the listed affected versions.
-
Verify ABAP Debugger accessAttempt to access the ABAP Debugger (transaction /h to start debugging) and use the 'Go to statement' function (Ctrl+G or menu path). Observe whether the system prompts for S_DEVELOP DEBUG 02 authorization.Affected if The 'Go to statement' function executes without prompting for S_DEVELOP DEBUG 02 authorization.
-
Inspect S_DEVELOP authorization objectUse transaction SU01 or SU56 to review user authorizations. Specifically check if the S_DEVELOP object includes the DEBUG 02 activity for the affected user profile.Affected if Users have debug access but the S_DEVELOP authorization with DEBUG 02 is not explicitly assigned or is missing.
-
Review debug authorization rolesUse transaction PFCG to examine the roles assigned to users who have debugging capability. Verify whether roles correctly require S_DEVELOP with DEBUG 02 for ABAP Debugger access.Affected if Roles grant debug functionality without the proper S_DEVELOP DEBUG 02 authorization object in the role definition.
A user is affected if their SAP kernel version is one of the listed affected versions AND they can access the ABAP Debugger 'Go to statement' function without being prompted for or possessing the S_DEVELOP DEBUG 02 authorization.
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 relevant SAP Kernel patches to enforce proper authorization checks for the 'Go to statement' functionality in the ABAP Debugger, and verify that user roles do not grant debug access without the S_DEVELOP DEBUG 02 authorization.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0349 — 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-0349 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