CVE-2019-0304
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 · uneditedFTP Function of SAP NetWeaver AS ABAP Platform, 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.45, 7.49, 7.53, 7.73, allows an attacker to inject code or specifically manipulated command that can be executed by the application. An attacker could thereby control the behaviour of the application.
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 command injection vulnerability exists in the FTP function of SAP NetWeaver AS ABAP Platform across multiple kernel versions (7.21-7.73). An attacker can inject malicious code or commands through the FTP functionality, potentially allowing complete control of the application due to the critical 9.8 CVSS score.
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.45= 7.49= 7.53= 7.73= 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.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 the SAP NetWeaver kernel versionLog into the SAP system and use transaction code SM51 to view the kernel release and version, or run the SAP kernel executable with version flags as documented in your system administration guideAffected if The kernel version matches 7.21, 7.45, 7.49, 7.53, 7.73, or any of the 7.21ext, 7.22, 7.22ext versions listed in the affected products
-
Confirm the specific kernel patch levelIn SM51, right-click the server process and select Release Notes, or use the SAP Kernel version command to see the exact patch number (e.g., 7.21, 7.45, etc.)Affected if The exact kernel version matches one of the versions listed in the affected products and versions section
-
Check if FTP functionality is configured or enabledReview the SAP system profile parameters for FTP-related settings (such as ftp/active_mode or similar FTP configuration parameters), or check the SAP Gateway service list for FTP portsAffected if FTP functionality is enabled or configured in the SAP environment, as this is required for the attack vector
-
Review FTP access permissionsUse transaction code SM37 or check user authorizations related to FTP command execution to determine which users can access the FTP functionAffected if Users with FTP access exist in the system, as the vulnerability is exploited through manipulating FTP commands
-
Verify kernel component typeConfirm whether the installed kernel is 32-bit (Krnl32nuc/Krnl32uc) or 64-bit (Krnl64nuc/Krnl64uc) and cross-reference with the affected versions list for that specific kernel typeAffected if The kernel component type and version combination matches any entry in the affected products list
The system is affected if it runs any of the listed vulnerable kernel versions AND has FTP functionality accessible to users who can manipulate FTP commands.
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.
dbcve · scopedApply the appropriate SAP security patch for CVE-2019-0304 to the affected NetWeaver kernel versions. Prioritize systems with exposed FTP functionality, as the attack vector requires manipulating FTP commands.
SAP Kernel 7.73 or latest available kernel patch as specified in the SAP Security Note
- 1. Access the SAP Launchpad Support Portal (launchpad.support.sap.com) and search for SAP Security Note related to CVE-2019-0304
- 2. Download the applicable SAP Kernel patch for your specific kernel version (KRNL32NUC, KRNL32UC, KRNL64NUC, KRNL64UC, or KERNEL)
- 3. Apply the patch following SAP's standard kernel update procedures
- 4. Restart the SAP NetWeaver AS ABAP Platform services to activate the patched kernel components
- 5. Verify the FTP function operates normally after patch application
- 6. Confirm the security fix by reviewing the patch release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0304 — 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-0304 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