dbcve.org
BusinessobjectsApplication · Sap

CVE-2022-28214

HIGH · 7.8 CVSS v3.1 Published 2022-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
During an update of SAP BusinessObjects Enterprise, Central Management Server (CMS) - versions 420, 430, authentication credentials are being exposed in Sysmon event logs. This Information Disclosure could cause a high impact on systems’ Confidentiality, Integrity, and Availability.

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

During SAP BusinessObjects Enterprise updates, the Central Management Server (CMS) versions 420 and 430 inadvertently writes authentication credentials to Windows Sysmon event logs, exposing sensitive authentication information that could be harvested by attackers with log access.

MitigationConfigure Sysmon to filter or redact credential data from event logs, and immediately rotate any credentials that may have been exposed. Review and purge existing Sysmon logs for credential exposure.

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:= 420= 430
Businessobjects Business IntelligenceApplication
Affected:= 420= 430

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 version
    Check the Windows Registry at HKLM\SOFTWARE\SAP BusinessObjects\CentralManagementServer\Version or inspect the SAP BusinessObjects installation directory for version information. Use 'reg query HKLM\SOFTWARE\SAP BusinessObjects' or check 'C:\Program Files (x86)\SAP BusinessObjects\' for version files.
    Affected if The installed version is exactly 420 or 430.
  2. Verify Central Management Server (CMS) is running
    Open Windows Services (services.msc) and locate the SAP BusinessObjects CMS service, or run 'sc query' to enumerate services containing 'CMS' or 'BusinessObjects' in the name.
    Affected if The CMS service is installed and running on versions 420 or 430.
  3. Confirm Sysmon is installed and capturing events
    Run 'Get-WinEvent -ListLog *Sysmon*' in PowerShell or open Event Viewer and navigate to Applications and Services Logs > Microsoft > Windows > Sysmon. Verify the log exists and has recent entries.
    Affected if Sysmon logging is enabled and operational.
  4. Examine Sysmon event logs for credential exposure
    Use PowerShell 'Get-WinEvent -LogName Microsoft-Windows-Sysmon/Operational | Select-Object -First 100' or open Event Viewer and search Sysmon logs for event IDs 10 (ProcessAccess) or 12-13 (Registry events) that may contain plaintext credentials or authentication tokens.
    Affected if Sysmon logs contain entries with authentication credentials, passwords, tokens, or sensitive authentication data in plaintext.
  5. Audit access permissions to Sysmon log files and directories
    Run 'Get-Acl 'C:\Windows\System32\winevt\Logs\Microsoft-Windows-Sysmon%4Operational.evtx' | Select-Object Owner,AccessToString' or use the Security event log to review who has read access to the Sysmon log directory.
    Affected if Untrusted users or groups have read access to Sysmon event logs.

You are affected if SAP BusinessObjects CMS versions 420 or 430 are running, Sysmon is installed, and authentication credentials are present in Sysmon logs accessible to unauthorized users.

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

Configure Sysmon to filter or redact credential data from event logs, and immediately rotate any credentials that may have been exposed. Review and purge existing Sysmon logs for credential exposure.

Fix this in Businessobjects 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-2022-28214 — 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-2022-28214 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