CVE-2019-0327
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 NetWeaver for Java Application Server - Web Container, (engineapi, versions 7.1, 7.2, 7.3, 7.31, 7.4 and 7.5), (servercode, versions 7.2, 7.3, 7.31, 7.4, 7.5), allows an attacker to upload files (including script files) without proper file format validation.
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 confidenceUnrestricted file upload vulnerability in SAP NetWeaver Java Application Server Web Container allows attackers to upload files without proper format validation, including executable script files that could lead to remote code execution.
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.10= 7.20= 7.30= 7.31= 7.40= 7.50CVSS 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.
-
Identify installed SAP NetWeaver Java AS versionExecute command: `sapcontrol -nr <instance> -function GetVersion` or check version via SAP MMC/LMDB. Alternatively, inspect file: `<SAPInstance>/exe/jvm-version.txt` or check `java -version` from the SAP JVM directoryAffected if The installed version matches 7.10, 7.20, 7.30, 7.31, 7.40, or 7.50
-
Verify Web Container HTTP service is runningExecute: `sapcontrol -nr <instance> -function GetProcessList` and look for processes `disp+work` and `icman` or check SAP MMC under Server > Processes. Also check if port 5<XX>08 (HTTP) or 5<XX>14 (HTTPS) is listening via `netstat -an | grep -E '5[0-9]{3}[08|14]'`Affected if The Web Container (HTTP service) is active and exposed on a network interface
-
Identify exposed file upload web applicationsInspect deployed web applications in SAP Visual Administrator: Server > Applications, or check directory `<SAPInstance>/j2ee/cluster/server<nr>/applications` for .war files. Review web.xml descriptors in each application's WEB-INF folder for servlet definitions related to file uploadAffected if File upload servlets or applications are deployed and accessible via HTTP(s)
-
Check upload directory script execution permissionsInspect the upload directory configuration in the web application's deployment descriptor or check the actual directory permissions. Default upload paths may be under `<SAPInstance>/j2ee/cluster/server<nr>/temp` or `<SAPInstance>/j2ee/cluster/server<nr>/work`. Run: `ls -la <upload_directory>` to check for execute permissionsAffected if Upload directories allow script execution (execute bit set or lack of restrictions)
You are affected if you run SAP NetWeaver Java AS version 7.10 through 7.50 with the Web Container enabled and have deployed web applications that accept file uploads without server-side allowlist validation.
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 dataImplement server-side file format validation with allowlists for permitted file types, and disable script execution permissions on upload directories.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0327 — 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-0327 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