LiveActive security incident?Get immediate response
CVE Record

CVE-2023-33992: Missing Authorization Check in SAP Business Warehouse and SAP BW/4HANA

The SAP BW BICS communication layer in SAP Business Warehouse and SAP BW/4HANA - version SAP_BW 730, SAP_BW 731, SAP_BW 740, SAP_BW 730, SAP_BW 750, DW4CORE 100, DW4CORE 200, DW4CORE 300, may expose unauthorized cell values to the data response. To be able to exploit this, the user still needs authorizations on the query as well as on the keyfigure/measure level. The missing check only affects the data level.

MediumCVSS 4.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let an already-authorized SAP BW user see data cell values they should not see. It is not a broad remote takeover issue, but it can expose sensitive reporting data where SAP BW authorizations are relied on for row or cell-level confidentiality.

Executive priority

Treat as a confidentiality-focused SAP analytics issue. Prioritize remediation where BW reports contain sensitive business or regulated data, but urgency is below internet-scale critical vulnerabilities because exploitation requires existing authorized access.

Technical view

CVE-2023-33992 is a missing authorization check in the SAP BW BICS communication layer. A user with query and keyfigure/measure authorization may receive unauthorized cell values in the data response. The issue affects the data level only in listed SAP_BW and DW4CORE versions.

Likely exposure

Exposure is likely limited to organizations running SAP Business Warehouse or SAP BW/4HANA on the listed SAP_BW or DW4CORE versions, especially where BICS queries expose sensitive financial, operational, or regulated reporting data.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires an authenticated user with existing query and keyfigure/measure authorizations, plus user interaction per the CVSS vector.

Researcher notes

The core risk is authorization bypass at the data-response level, not query or measure authorization bypass. Evidence does not support claims of unauthenticated access, integrity impact, availability impact, public exploit availability, or active exploitation.

Mitigation direction

  • Identify SAP BW and BW/4HANA systems running the listed SAP_BW or DW4CORE versions.
  • Review SAP Note 3088078 and apply SAP's recommended correction guidance.
  • Limit query and keyfigure/measure authorizations to users with a clear business need.
  • Prioritize reports containing financial, personal, regulated, or executive-sensitive data.

Validation and detection

  • Inventory installed SAP_BW and DW4CORE component versions on BW systems.
  • Confirm whether SAP Note 3088078 is implemented on each affected system.
  • Review BICS-accessible queries for sensitive data exposure risk.
  • Test authorization boundaries with approved accounts that have query and measure access.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-33992 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N0.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.5Medium
CVSS 3.1 vector shape for CVE-2023-33992Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SAP_SESAP Business Warehouse and SAP BW/4HANASAP_BW 730, SAP_BW 731, SAP_BW 740, SAP_BW 750, DW4CORE 100, DW4CORE 200, DW4CORE 300unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.