dbcve.org
Businessobjects Business IntelligenceApplication · Sap

CVE-2018-2445

CRITICAL · 9.6 CVSS v3.0 Published 2018-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
AdminTools in SAP BusinessObjects Business Intelligence, versions 4.1, 4.2, allows an attacker to manipulate the vulnerable application to send crafted requests on behalf of the application, resulting in a Server-Side Request Forgery (SSRF) vulnerability.

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

Server-Side Request Forgery (SSRF) vulnerability in AdminTools component of SAP BusinessObjects Business Intelligence versions 4.1 and 4.2 allows attackers to manipulate the application to send crafted requests on behalf of the server, potentially enabling internal network reconnaissance, access to internal services, or cloud metadata exfiltration.

MitigationImplement strict allowlist-based validation for all URL/URI inputs in AdminTools, restrict outbound network connections from the application server, and consider network segmentation to limit potential SSRF impact on internal resources.

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 Business IntelligenceApplication
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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 SAP BusinessObjects BI version
    Check the installed version of SAP BusinessObjects Business Intelligence platform. This is typically visible in the CMC (Central Management Console) under 'About SAP BusinessObjects' or via command line: '<bobj_install_dir>/sap_businessobjects/enterprise_xi41/win32_x86/installfiles/setup.exe' -version or check version info in the CMC welcome page.
    Affected if Version is exactly 4.1 or 4.2 (these are the affected versions)
  2. Confirm AdminTools component presence
    Verify that the AdminTools component is installed on the system. AdminTools is part of the SAP BusinessObjects BI platform and provides administrative functionality. Check for the presence of AdminTools-related files in the installation directory under '<bobj_install_dir>/sap_businessobjects/BI platform/admintools/' or verify through the CMC under 'AdminTools' node.
    Affected if AdminTools component is installed and accessible
  3. Check AdminTools URL accessibility
    Determine if the AdminTools interface is network-accessible. Access the AdminTools URL pattern typically at 'http(s)://<server>:<port>/AdminTools' or check via CMC to see if the web application is enabled and exposed.
    Affected if AdminTools web interface is enabled and reachable over network
  4. Review outbound network configuration
    Examine the server's ability to make outbound HTTP/HTTPS connections. Check if the BusinessObjects application server has unrestricted outbound network access, which would be required for an SSRF attack to reach internal resources or cloud metadata endpoints.
    Affected if Server has outbound network access enabled from the application tier

You are affected if you are running SAP BusinessObjects BI version 4.1 or 4.2 with the AdminTools component installed and network-accessible, allowing potential SSRF exploitation.

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

Implement strict allowlist-based validation for all URL/URI inputs in AdminTools, restrict outbound network connections from the application server, and consider network segmentation to limit potential SSRF impact on internal resources.

Fix this in Businessobjects Business Intelligence Scoped from the published advisory
  • Consultation10.0 h
  • Implementation20.0 h
  • Testing14.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,140
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2445 — 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-2445 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