CVE-2019-0248
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 · uneditedUnder certain conditions SAP Gateway of ABAP Application Server (fixed in SAP_GWFND 7.5, 7.51, 7.52, 7.53; SAP_BASIS 7.5) allows an attacker to access information which would otherwise be restricted.
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 confidenceInformation disclosure vulnerability in SAP Gateway of ABAP Application Server that allows an attacker to access restricted information under certain conditions. The specific attack vector and authentication requirements are not detailed in available sources.
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.5= 7.51= 7.52= 7.53= 7.5CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 NetWeaver versionExecute transaction code SM51 or use SAP system information to display the installed SAP NetWeaver release version. Look for version numbers 7.5, 7.51, 7.52, or 7.53.Affected if The displayed NetWeaver version matches exactly 7.5, 7.51, 7.52, or 7.53
-
Check SAP Basis versionExecute transaction code SM51 or use system report to display the SAP Basis version. In SAP system information, locate the SAP Basis component version.Affected if The installed SAP Basis version is 7.5
-
Verify SAP Gateway component is activeUse transaction code SMGW to access the SAP Gateway monitor. Check if the Gateway is running and accessible on the system.Affected if SAP Gateway is active and running on the affected NetWeaver or Basis version listed above
-
Confirm system type is ABAP Application ServerUse transaction code SM51 to view the system type. Verify it is an ABAP Application Server (AS ABAP) rather than a Java-only system.Affected if The system runs ABAP Application Server and meets the version conditions above
A user is affected if their SAP NetWeaver shows version 7.5, 7.51, 7.52, or 7.53, or their SAP Basis shows version 7.5, particularly when running SAP Gateway on an ABAP Application Server.
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 patches for SAP_GWFND versions 7.5, 7.51, 7.52, 7.53 or SAP_BASIS 7.5 as appropriate to the deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0248 — 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-0248 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