dbcve.org
Businessobjects Business IntelligenceApplication · Sap

CVE-2022-32244

MEDIUM · 5.2 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
54/100
Remediation priority · Moderate
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
Under certain conditions an attacker authenticated as a CMS administrator access the BOE Commentary database and retrieve (non-personal) system data, modify system data but can't make the system unavailable. This needs the attacker to have high privilege access to the same physical/logical network to access information which would otherwise be restricted, leading to low impact on confidentiality and high impact on integrity of the application.

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

In SAP BusinessObjects Enterprise (BOE), a CMS administrator with high-privilege network access can bypass intended restrictions to access and modify the BOE Commentary database. This is an improper access control vulnerability allowing unauthorized data modification (high integrity impact) alongside limited data exfiltration (low confidentiality impact).

MitigationImplement strict role-based access controls (RBAC) for the CMS administrator role, enforce network segmentation to limit privileged access paths, and apply principle of least privilege to restrict database access permissions.

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

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:H/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 SAP BusinessObjects version
    Locate the SAP BusinessObjects installation directory and check the version. Common paths include C:\Program Files\SAP BusinessObjects\ or /opt/sap_businessobjects/. Look for version files or check the CMC (Central Management Console) about page. The affected versions are 420 and 430.
    Affected if The installed version matches 420 or 430 exactly.
  2. Verify CMS administrator accounts exist
    Access the Central Management Console (CMC) and navigate to Users and Groups. Look for accounts assigned the 'Administrator' role or those with CMS full administrative rights. Query the CMS system database (CMS_<sid>) for accounts with administrative privileges using SQL or the SAP BusinessObjects SDK.
    Affected if A CMS administrator account exists in the system.
  3. Check network access configuration for privileged accounts
    Review network segmentation and access control lists (ACLs) governing CMS communication ports (default 6400 for Tomcat, 8080 for HTTP). Examine server configuration files (e.g., boe.war deployment descriptors, Tomcat server.xml) and firewall rules to determine if high-privilege network paths exist to the CMS.
    Affected if The CMS is accessible over the network to accounts with administrator privileges without sufficient network-level restrictions.
  4. Inspect Commentary database access controls
    Access the CMC and navigate to the Commentary application settings or check the underlying database connection. Examine the ODBC/JDBC data source configuration for the Commentary database and review user permissions on that database object. The Commentary database is typically stored in the CMS repository.
    Affected if The Commentary database can be accessed or modified by a CMS administrator without proper role-based restrictions, or modifications can be made without audit trail.

If SAP BusinessObjects Business Intelligence version 420 or 430 is installed and a CMS administrator has high-privilege network access to the system, the environment is likely affected by this improper access control vulnerability allowing unauthorized Commentary database modification.

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 strict role-based access controls (RBAC) for the CMS administrator role, enforce network segmentation to limit privileged access paths, and apply principle of least privilege to restrict database access permissions.

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-2022-32244 — 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-32244 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