CVE-2020-6283
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 Fiori Launchpad does not sufficiently encode user controlled inputs, and hence allowing the attacker to inject the meta tag into the launchpad html using the vulnerable parameter, resulting in reflected Cross-Site Scripting (XSS) vulnerability. With a successful attack, the attacker can steal authentication information of the user, such as data relating to his or her current session.
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 confidenceSAP Fiori Launchpad contains a reflected Cross-Site Scripting (XSS) vulnerability where user-controlled inputs are not properly encoded, allowing attackers to inject meta tags into the launchpad HTML through a vulnerable parameter. This enables theft of authentication credentials and session data.
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= 750= 752= 753= 754= 755CVSS 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.
-
Identify SAP Fiori Launchpad installationCheck your SAP system for Fiori Launchpad components. Look for Fiori-related web applications in your SAP gateway or front-end server. Verify the presence of /sap/bc/ui5_ui5 or similar Fiori UI5 paths in your web server configuration.Affected if SAP Fiori Launchpad is not installed on the system
-
Determine Fiori Launchpad versionAccess the SAP Fiori Launchpad and check the version information, typically found in the system information or about section. Alternatively, check the SAP UI5 library version loaded by the launchpad, which often correlates with the Fiori Launchpad version.Affected if The installed version matches 750, 752, 753, 754, or 755
-
Verify if the vulnerable parameter is accessibleExamine the Fiori Launchpad URL parameters during normal usage. The vulnerability involves user-controlled inputs not being encoded. Check if parameters passed to the launchpad (such as those in the URL hash or query string) can be observed and analyzed.Affected if User-controllable parameters are passed to the launchpad without visible encoding
-
Check for meta tag injection pointAnalyze the HTML response when accessing the Fiori Launchpad with test input in the URL parameters. Look for any location where meta tags or HTML elements could be injected through the URL.Affected if The launchpad reflects user input in the HTML response without proper encoding
The system is affected if SAP Fiori Launchpad is installed and the installed version is one of 750, 752, 753, 754, or 755, with user-controlled parameters accessible through the launchpad URL.
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 proper output encoding for all user-controlled inputs in the Fiori Launchpad, and implement input validation. Deploy SAP security patches for CVE-2020-6283 once available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6283 — 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-6283 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