dbcve.org
Businessobjects Bi PlatformApplication · Sap

CVE-2018-2467

MEDIUM · 5.3 CVSS v3.0 Published 2018-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In the Software Development Kit in SAP BusinessObjects BI Platform Servers, versions 4.1 and 4.2, using the specially crafted URL in a Web Browser such as Chrome the system returns an error with the path of the used application server.

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 confidence

In SAP BusinessObjects BI Platform SDK versions 4.1 and 4.2, specially crafted URLs cause the system to return error messages that disclose the full server path of the application. This is a path disclosure/information disclosure vulnerability where error handling fails to sanitize server path information before displaying it to users.

MitigationConfigure custom error pages or modify error handling to suppress detailed server path information from being displayed in error messages. Ensure Web tier configuration masks filesystem paths.

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
Businessobjects Bi PlatformApplication
Affected:= 4.1= 4.2

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SAP BusinessObjects BI Platform SDK version
    Check the SAP BusinessObjects BI Platform SDK version installed in your environment through the SAP BI launcher, SAP BusinessObjects Central Management Console (CMC), or the installed product documentation. Look for version information in the SDK libraries or platform components.
    Affected if The installed version is 4.1 or 4.2 specifically (these are the only affected versions listed)
  2. Locate the web application entry points
    Identify the web tier URLs used to access the SAP BusinessObjects BI Platform, typically through the Tomcat or Java-based web server hosting the SDK. Common paths include /BOE/BI or similar endpoints.
    Affected if The web tier is exposed and accessible to users
  3. Trigger error conditions with specially crafted requests
    Send malformed or unexpected requests to the BI Platform web URLs, such as invalid parameters, missing path segments, or requests to non-existent resources. Observe the HTTP response and any error pages returned.
    Affected if Error messages are returned to the user without sanitization
  4. Examine error message content for path disclosure
    Inspect any error pages, stack traces, or diagnostic messages returned by the application. Look for filesystem path strings such as C:\, /usr/, /sap/, or similar directory structures that would reveal server-side directory locations.
    Affected if Error responses contain full server filesystem paths (the vulnerability is present)
  5. Verify error handling configuration
    Check the web tier configuration files (such as web.xml, error pages configuration, or custom error handlers) to determine whether custom error pages are defined or if default server error pages are being used.
    Affected if No custom error pages are configured and default error handling is in use

You are affected if you are running SAP BusinessObjects BI Platform SDK version 4.1 or 4.2 AND your error responses expose server filesystem paths to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure custom error pages or modify error handling to suppress detailed server path information from being displayed in error messages. Ensure Web tier configuration masks filesystem paths.

Fix this in Businessobjects Bi Platform Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-2467 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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