dbcve.org
Financial Consolidation Cube DesignerApplication · Sap

CVE-2018-2499

HIGH · 7.5 CVSS v3.0 Published 2019-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
A security weakness in SAP Financial Consolidation Cube Designer (BOBJ_EADES fixed in versions 8.0, 10.1) may allow an attacker to discover the password hash of an admin user.

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

A security weakness in SAP Financial Consolidation Cube Designer (BOBJ_EADES) allows unauthenticated attackers to discover password hashes of administrator users through the affected component, potentially enabling offline password cracking and unauthorized system access.

MitigationUpgrade SAP Financial Consolidation Cube Designer to versions 8.0 or 10.1 where the vulnerability is fixed, and immediately rotate credentials for any admin accounts that may have been exposed.

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
Financial Consolidation Cube DesignerApplication
Affected:= 10.1
Financial Consolidation Cube Designer Bobj EadesApplication
Affected:= 8.0

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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 if SAP Financial Consolidation Cube Designer is installed
    Check for the presence of the application in the system. Look for installation directories named typically under SAP or BusinessObjects paths, or query the system's installed software inventory.
    Affected if The software is installed and the version falls within the affected ranges (version 10.1 or any version 8.0 of the Bobj Eades component).
  2. Determine the installed version of SAP Financial Consolidation Cube Designer
    Locate the version information in the software's About dialog, readme files, or check version metadata in the installation directory. Compare against the affected version 10.1 for the base product or version 8.0 for the Bobj Eades component.
    Affected if The installed version matches exactly 10.1 for the base product or exactly 8.0 for the Bobj Eades component.
  3. Verify if the BOBJ_EADES component web service is exposed
    Check the SAP BusinessObjects or Financial Consolidation server configuration for exposed web services. Inspect the web.xml or analogous configuration files in the application server to determine if the BOBJ_EADES endpoint is accessible over HTTP/HTTPS without authentication.
    Affected if The BOBJ_EADES web service endpoint is accessible without requiring authentication.
  4. Review access logs for the BOBJ_EADES endpoint
    Examine the application server access logs and web server logs for requests targeting the BOBJ_EADES component path. Look for unusual or unauthorized access patterns from external IP addresses.
    Affected if There are unauthorized or unexpected requests to the BOBJ_EADES endpoint in the logs.
  5. Inspect for exposed password hash files
    Check the BOBJ_EADES component directory and related configuration folders for any files that may contain password hashes or user credential information that could be served over the network.
    Affected if Password hash files or user credential data is accessible through the BOBJ_EADES component or stored in world-readable locations within the component directory.

A user is affected if SAP Financial Consolidation Cube Designer version 10.1 or the BOBJ_EADES component version 8.0 is installed with the BOBJ_EADES web service exposed without authentication, or if evidence of unauthorized access to password hashes is found in logs or file system.

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

Upgrade SAP Financial Consolidation Cube Designer to versions 8.0 or 10.1 where the vulnerability is fixed, and immediately rotate credentials for any admin accounts that may have been exposed.

Fix this in Financial Consolidation Cube Designer 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-2499 — 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-2499 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