CVE-2020-6319
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 Application Server Java, versions - 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, and 7.50 allows an unauthenticated attacker to include JavaScript blocks in any web page or URL with different symbols which are otherwise not allowed. On successful exploitation an attacker can steal authentication information of the user, such as data relating to his or her current session and limitedly impact confidentiality and integrity of the application, leading to Reflected Cross Site Scripting.
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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Application Server Java allows unauthenticated attackers to inject malicious JavaScript by bypassing existing sanitization filters using alternate symbols. Successful exploitation enables session hijacking and theft of user authentication credentials.
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.11= 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm SAP NetWeaver AS Java is installedCheck for SAP NetWeaver Application Server Java processes or inspect installed software components using SAP JVM version command: java -version, or check SAP MMC/Management console for 'SAP NetWeaver Application Server Java' componentAffected if The system runs SAP NetWeaver Application Server Java as a component
-
Identify the NetWeaver AS Java versionAccess SAP Management Console or run SAP command 'sm51' to retrieve the NetWeaver release version, or inspect the installed SAP bundle version in the system propertiesAffected if The installed version matches 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50
-
Verify web applications are exposedCheck if the SAP NetWeaver AS Java HTTP port is listening and accessible (default ports 50000, 50001, or custom HTTP/HTTPS ports configured in the SAP ICM). Use netstat or SAP transaction SMICM to view open portsAffected if HTTP/HTTPS ports for NetWeaver are open and accessible from a network where untrusted users could send requests
-
Test for XSS in web parametersSend a crafted request with alternate symbols like modified Unicode or encoded characters in URL parameters to the SAP web interface (e.g., /webdynpro/ paths). Observe if the application reflects unsanitized input in the response without proper encodingAffected if User-supplied parameters are reflected in the response without sanitization or encoding, allowing script injection
You are affected if your environment runs SAP NetWeaver Application Server Java versions 7.10 through 7.50 and has accessible HTTP/HTTPS web interfaces that reflect user input without proper encoding.
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 security patches for CVE-2020-6319 immediately. As a compensating control, implement robust input validation and output encoding on all user-supplied parameters in web applications until the patch is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6319 — 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-2020-6319 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