dbcve.org
BusinessobjectsApplication · Sap

CVE-2018-2408

HIGH · 7.3 CVSS v3.0 Published 2018-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Session Management in SAP Business Objects, 4.0, from 4.10, from 4.20, 4.30, CMC/BI Launchpad/Fiorified BI Launchpad. In case of password change for a user, all other active sessions created using older password continues to be active.

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 Business Objects, when a user's password is changed, existing active sessions authenticated with the old password are not invalidated. This allows attackers who have obtained session tokens prior to a password change to continue using those sessions to access the system with the old (now invalid) credentials.

MitigationApply the relevant SAP security patch for CVE-2018-2408. Until patched, administrators should manually terminate all active sessions or restart the affected SAP Business Objects services after any password change to invalidate stale sessions.

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
BusinessobjectsApplication
Affected:= 4.0= 4.10= 4.20= 4.30

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
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 Business Objects installation
    Locate the SAP Business Objects installation directory or check system inventory for 'SAP BusinessObjects' or 'BusinessObjects' software packages. On Windows, look in Program Files or the SAP installation root. On Unix/Linux, check /opt/sap or custom installation paths.
    Affected if SAP Business Objects software is installed on the system
  2. Determine installed BusinessObjects version
    Check the version of the installed SAP Business Objects installation. This is typically found in a version file within the installation directory, or accessible via the SAP BusinessObjects Central Management Console (CMC) under 'About'. Common locations include a version.properties file or the CMC > Administration > License Keys screen.
    Affected if The installed version matches 4.0, 4.10, 4.20, or 4.30, or falls within the 4.0 through 4.30 release family
  3. Review active session inventory
    Access the SAP BusinessObjects Central Management Console (CMC) and navigate to the 'Sessions' section under the 'Applications' or 'Server' category to view currently authenticated sessions. Alternatively, use the CMC 'Sessions' management screen to list all active user sessions with their session IDs, login times, and associated user accounts.
    Affected if Multiple active sessions exist for user accounts that have had password changes performed since those sessions were created
  4. Verify session termination after password change
    After a test password change for a test account, use the CMC Sessions management to check whether any sessions authenticated with the old password remain active. Note the session IDs before the password change and compare against active sessions after the change.
    Affected if Sessions authenticated with the old password remain active after a password change has been performed

The environment is affected if SAP Business Objects versions 4.0 through 4.30 are installed and active user sessions persist after password changes have been performed.

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

Apply the relevant SAP security patch for CVE-2018-2408. Until patched, administrators should manually terminate all active sessions or restart the affected SAP Business Objects services after any password change to invalidate stale sessions.

Fix this in Businessobjects Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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