CVE-2022-39800
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 BusinessObjects BI LaunchPad - versions 420, 430, is susceptible to script execution attack by an unauthenticated attacker due to improper sanitization of the user inputs while interacting on the network. On successful exploitation, an attacker can view or modify information causing a limited impact on confidentiality and integrity 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 · moderate confidenceCross-site scripting (XSS) vulnerability in SAP BusinessObjects BI LaunchPad versions 420 and 430 allows unauthenticated attackers to execute malicious scripts due to improper sanitization of user inputs. Successful exploitation permits viewing or modifying information with limited impact on confidentiality and integrity.
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= 420= 430CVSS 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 BusinessObjects BI LaunchPad installationLocate the SAP BusinessObjects BI installation directory or check running services for BusinessObjects components. Look for the 'BOE' or 'BusinessObjects' process or service on the system.Affected if SAP BusinessObjects BI LaunchPad is installed and running on the server
-
Determine the installed versionCheck the SAP BusinessObjects version by reviewing installation logs, the version.properties file in the installation directory, or the SAP BusinessObjects Central Management Console (CMC) about page.Affected if The installed version is exactly 420 or exactly 430 (these are the affected versions)
-
Verify the BI LaunchPad web interface is accessibleConfirm that the BI LaunchPad web application is accessible by accessing the LaunchPad URL (typically /BOE/BI or /lap) and that the application responds to HTTP requests.Affected if The BI LaunchPad web interface is exposed and accepts user input through web requests
-
Check for unauthenticated access to input fieldsReview the BI LaunchPad login page and any publicly accessible input parameters to identify where user-supplied data is processed without sanitization.Affected if The application accepts user input without authentication or proper input validation on the web interface
The environment is affected if SAP BusinessObjects BI LaunchPad version 420 or 430 is installed and the web interface is accessible, allowing unauthenticated user input to be processed without proper sanitization.
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-2022-39800 when available. Until then, implement input validation and output encoding at the application layer, or deploy a WAF rule to filter malicious script payloads.
- 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-2022-39800 — 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-2022-39800 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