dbcve.org
Businessobjects Business IntelligenceApplication · Sap

CVE-2019-0348

MEDIUM · 6.5 CVSS v3.0 Published 2019-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 →
71/100
Remediation priority · Elevated
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
SAP BusinessObjects Business Intelligence Platform (Web Intelligence), versions 4.1, 4.2, can access database with unencrypted connection, even if the quality of protection should be encrypted.

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

SAP BusinessObjects Web Intelligence (versions 4.1, 4.2) fails to enforce encrypted database connections as configured, allowing unencrypted communication even when the quality of protection setting specifies encryption should be used. This bypass of the intended security control exposes sensitive data in transit between the Web Intelligence layer and the underlying database.

MitigationApply the relevant SAP security patch and verify that database connections are actually using encryption (TLS/SSL) by inspecting network traffic or database connection strings.

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

CVSS:3.0/AV:N/AC:L/PR:L/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 installed SAP BusinessObjects version
    Check the installed version of SAP BusinessObjects Business Intelligence in the Central Management Console (CMC) under 'About SAP BusinessObjects' or via the SAP BI platform management tools. Compare the exact version number to 4.1 and 4.2.
    Affected if The installed version is exactly 4.1 or 4.2 (any patch level within these major versions).
  2. Locate Quality of Protection configuration
    In the Central Management Console (CMC), navigate to the database connection configuration for Web Intelligence data sources. Look for the 'Quality of Protection' or 'Security' settings in the connection parameters.
    Affected if The Quality of Protection setting is configured to require encryption (such as 'Encrypted' or 'Integrity and Encryption') but the actual connections are unencrypted.
  3. Verify database connection encryption is active
    Inspect actual network traffic between the Web Intelligence processing servers and the underlying databases using network packet capture tools (such as Wireshark) or review database connection string parameters in the configuration files.
    Affected if Network traffic between Web Intelligence and the database is unencrypted (plaintext) despite the quality of protection setting specifying encryption should be used.
  4. Review database connection configuration files
    Locate and examine the database connection configuration files for the Web Intelligence reporting layer. Check the connection string parameters for the 'encrypt' or 'ssl' flags and compare them to the intended security settings.
    Affected if The configuration files show encryption flags set to false or missing despite the quality of protection being configured for encrypted connections.

You are affected if running version 4.1 or 4.2 AND the quality of protection setting specifies encryption but actual database traffic is transmitted unencrypted.

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 and verify that database connections are actually using encryption (TLS/SSL) by inspecting network traffic or database connection strings.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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