CVE-2019-0365
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 (RFC), KRNL32NUC, KRNL32UC and KRNL64NUC before versions 7.21, 7.21EXT, 7.22, 7.22EXT, KRNL64UC, before versions 7.21, 7.21EXT, 7.22, 7.22EXT, 7.49, 7.73 and KERNEL before versions 7.21, 7.49, 7.53, 7.73, 7.76 SAP GUI for Windows (BC-FES-GUI) before versions 7.5, 7.6, and SAP GUI for Java (BC-FES-JAV) before version 7.5, allow an attacker to prevent legitimate users from accessing a service, either by crashing or flooding the service.
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 confidenceDenial of Service vulnerability in SAP Kernel (RFC) and SAP GUI components allows attackers to crash or flood services, preventing legitimate user access. The vulnerability affects multiple SAP Kernel versions and SAP GUI for Windows/Java versions.
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.49= 7.53= 7.73= 7.76= 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.73CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Kernel versionRun 'sapkernel -v' or 'disp+work -v' on the SAP server, or check the kernel version file in the /sapmnt/<SID>/exe directoryAffected if Installed Kernel version equals 7.21, 7.49, 7.53, 7.73, or 7.76 (for Kernel), or 7.21, 7.21ext, 7.22, 7.22ext (for Krnl32nuc/Krnl32uc/Krnl64nuc/Krnl64uc), or 7.49/7.73 (for Krnl64uc)
-
Identify SAP GUI versionIn Windows, check 'Programs and Features' for SAP GUI version, or in SAP Logon go to 'Help > About SAP GUI'. For Java GUI, check via Java Control Panel or run 'guilogon -v'Affected if Installed SAP GUI version equals affected versions (specific GUI versions not listed but vulnerability affects SAP GUI for Windows/Java)
-
Verify RFC functionality is in useCheck SAP system configuration for active RFC destinations via transaction SM59, or review ABAP programs using RFC-enabled function modules (RFCDES, RFCEXEC, etc.)Affected if RFC destinations are configured or RFC-enabled ABAP code is deployed in the system
-
Check Kernel patch levelUse transaction SPAM to view installed kernel patches, or check the detailed kernel version via 'kernel.details' in the /sapmnt directoryAffected if Kernel patch level is below the fixed versions (7.21 must have patch >= 300, 7.49 >= 200, 7.53 >= 100, 7.73 >= 100, 7.76 >= 100)
The environment is affected if either the SAP Kernel version or SAP GUI version matches the listed affected versions AND RFC functionality is enabled or accessible.
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 vendor-supplied patches to SAP Kernel and SAP GUI components, upgrading to the specified minimum fixed versions (Kernel 7.21/7.49/7.53/7.73/7.76, GUI 7.5/7.6 depending on component).
- Consultation4.0 h
- Implementation12.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 $7,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0365 — 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-0365 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