dbcve.org
Businessobjects Business IntelligenceApplication · Sap

CVE-2018-2442

HIGH · 8.8 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 →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 SAP BusinessObjects Business Intelligence, versions 4.0, 4.1 and 4.2, while viewing a Web Intelligence report from BI Launchpad, the user session details captured by an HTTP analysis tool could be reused in a HTML page while the user session is still valid.

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 confidence

Session hijacking vulnerability in SAP BusinessObjects BI platform where user session details captured via HTTP analysis tools can be replayed in HTML pages while the session remains valid, allowing unauthorized actions within the authenticated user's context.

MitigationImplement proper session token randomization and regeneration, enforce secure session management practices, and validate session tokens on each request to prevent reuse of captured credentials.

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.0= 4.1= 4.2
Internet Graphics ServerApplication
Affected:= 7.20= 7.20ext= 7.45= 7.49= 7.53

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Identify installed SAP BusinessObjects BI version
    Access the SAP BusinessObjects Central Management Console (CMC) and navigate to the 'About' section, or check the version via the SAP BusinessObjects Installation Manager. For command-line, check the version.properties or version.txt files in the installation directory.
    Affected if The installed version is 4.0, 4.1, or 4.2 (any SP or patch level)
  2. Identify installed SAP Internet Graphics Server version
    Check the IGS version by accessing the server directly or reviewing the installation files. The version is typically visible in the SAP IGS welcome page or via the IGS administration interface.
    Affected if The installed version is 7.20, 7.20ext, 7.45, 7.49, or 7.53 (any SP or patch level)
  3. Examine session token characteristics
    Log into the SAP BusinessObjects web application, capture the session cookie (typically BVSAPISID or similar session identifiers) using browser developer tools or a proxy, and analyze whether the session ID appears predictable, static, or lacks sufficient randomness across multiple sessions.
    Affected if Session tokens are predictable, have low entropy, or remain the same across different user sessions
  4. Verify session token regeneration on re-authentication
    Log out and log back in with the same credentials, then compare the new session cookie value with the previous one. Check if the session ID changes after re-authentication or if the same token remains valid.
    Affected if Session tokens are NOT regenerated after logout/login or remain valid after re-authentication
  5. Check for session token reuse across requests
    Using an HTTP proxy (such as Burp Suite or Fiddler), capture a valid session token from one user session and attempt to replay it in a new browser session. Observe whether the replayed token is accepted and grants access.
    Affected if Replayed session tokens from captured HTTP traffic are accepted and grant authenticated access

Your environment is affected if you are running any version of SAP BusinessObjects BI 4.0-4.2 or SAP Internet Graphics Server 7.20-7.53 AND your session tokens can be captured and replayed to gain unauthorized access while the original session remains active.

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 proper session token randomization and regeneration, enforce secure session management practices, and validate session tokens on each request to prevent reuse of captured credentials.

Fix this in Businessobjects Business Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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