CVE-2022-41267
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 Business Objects Platform - versions 420, and 430, allows an attacker with normal BI user privileges to upload/replace any file on Business Objects server at the operating system level, enabling the attacker to take full control of the system causing a high impact on confidentiality, integrity, and availability 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 · high confidenceThis is an authenticated file upload/write vulnerability in SAP Business Objects Platform versions 420 and 430. An attacker with normal BI user privileges can upload or replace arbitrary files on the server's operating system, effectively achieving remote code execution and full system compromise.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 SAP Business Objects installationLocate the SAP Business Objects installation directory, typically under the SAP or BusinessObjects folder in Program Files on Windows, or /opt or /usr/sap on Linux/Unix. Check for common BI platform components like CMC (Central Management Console) or BOE (BusinessObjects Enterprise).Affected if SAP Business Objects Platform is installed on the system
-
Check installed version numberAccess the SAP Business Objects Central Management Console (CMC) or check the version via the SAP BusinessObjects installation files. In CMC, go to About or check the version information in the system details. Alternatively, inspect version files in the installation directory.Affected if The installed version is exactly 420 or exactly 430
-
Verify file upload capability is accessibleLocate the file upload or document upload feature within the SAP Business Objects web interface (CMC or BI Launch Pad). Check if the Document Repository or File Upload service is enabled and accessible to standard BI users.Affected if File upload functionality is enabled and accessible to regular BI users without elevated privileges
-
Confirm user privilege level for upload operationsReview the role assignments and rights within the CMC. Specifically check if standard BI users (non-admin accounts) have permissions to upload, publish, or replace documents or files through the platform.Affected if Normal BI user accounts possess file upload or file write permissions on the platform
-
Inspect web application configurationExamine the SAP Business Objects web configuration files (such as web.xml or configuration files in the webapps directory) for the file upload servlet or endpoint mappings. Verify if unrestricted file write operations are permitted.Affected if File upload servlet is exposed and permits write operations to arbitrary server paths
A system is affected if SAP Business Objects Platform version 420 or 430 is installed, the file upload feature is enabled, and normal (non-admin) BI users have permissions to upload or write files to the 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 the relevant SAP security patch immediately. Additionally, restrict file upload functionalities to only trusted users, implement strict file type validation, and review access controls to limit privileged operations.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41267 — 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-41267 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