CVE-2023-27894
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 Business Intelligence Platform (Web Services) - versions 420, 430, allows an attacker to inject arbitrary values as CMS parameters to perform lookups on the internal network which is otherwise not accessible externally. On successful exploitation, attacker can scan internal network to determine internal infrastructure for further attacks like remote file inclusion, retrieve server files, bypass firewall and force the vulnerable server to execute malicious requests, resulting in sensitive information disclosure. This causes limited impact on confidentiality of data.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in SAP BusinessObjects BI Platform's Web Services component. Attackers can inject arbitrary values as CMS parameters to force the server to perform lookups on internal network resources that would otherwise be inaccessible. This enables internal network reconnaissance, potential remote file inclusion, file retrieval, and firewall bypass for further attacks.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Platform versionUse SAP administration tools or system information utilities to determine the installed version of SAP BusinessObjects Business IntelligenceAffected if Installed version is 420 or 430
-
Confirm Web Services component is enabledVerify that the Web Services component is accessible and operational on the SAP BusinessObjects serverAffected if Web Services component is enabled and reachable
-
Inspect CMS parameter handlingReview the CMS configuration and examine how parameters are processed in Web Services requests for potential lack of input validationAffected if CMS parameters accept arbitrary values without validation or sanitization
-
Review network access from serverCheck outbound network access capabilities of the BusinessObjects server to internal network resourcesAffected if Server can make arbitrary network connections to internal systems
Environment is affected if running SAP BusinessObjects BI Platform version 420 or 430 with Web Services enabled and CMS parameters lack input validation, allowing SSRF exploitation.
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.
dbcve · scopedImplement strict input validation and sanitization for CMS parameters to prevent arbitrary value injection. Additionally, apply network segmentation and firewall rules to restrict the server's ability to make arbitrary network connections, limiting the impact of SSRF attacks.
SAP BusinessObjects BI Platform 4.2 SP6 or later / 4.3 SP1 or later (specific patch version per SAP Security Note)
- 1. Access the SAP Support Portal at https://launchpad.support.sap.com/
- 2. Search for the SAP Security Note related to CVE-2023-27894 (SAP Note number should be obtained from SAP)
- 3. Download and apply the relevant patch/service pack for SAP BusinessObjects BI Platform 4.2 (version 420) or 4.3 (version 430)
- 4. After applying the patch, restart the SIA (Server Intelligence Agent) and CMS services
- 5. Verify the fix by reviewing the applied patches in SAP BusinessObjects Central Management Console (CMC) under 'Servers' > 'Server Intelligence Agent'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27894 — 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-2023-27894 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