CVE-2023-28764
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 · uneditedSAP BusinessObjects Platform - versions 420, 430, Information design tool transmits sensitive information as cleartext in the binaries over the network. This could allow an unauthenticated attacker with deep knowledge to gain sensitive information such as user credentials and domain names, which may have a low impact on confidentiality and no impact on the integrity and availability of the system.
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 confidenceThe Information Design Tool component in SAP BusinessObjects Platform versions 420 and 430 transmits sensitive data (user credentials, domain names) as cleartext in binaries over the network. An attacker with deep network knowledge could intercept this traffic to obtain authentication credentials.
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= 4.20= 4.30CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP BusinessObjects Platform versionCheck the installed SAP BusinessObjects Platform version through the SAP BI Platform CMC (Central Management Console) or by inspecting the installation directory for version information. Use command: <SAP_INST_DIR>/sapbusinessobjects/enterprise_xi40/java/lib/ but do not rely on this path alone if installed elsewhere.Affected if Version equals exactly 4.20 or 4.30 as shown in the CMC or installation metadata
-
Confirm Information Design Tool component is deployedLocate the Information Design Tool (IDT) executable or installation on the system. Typically found in the SAP BusinessObjects installation directory under sapbusinessobjects/InformationDesignTool/ or check if the IDT client software is installed on the machine.Affected if Information Design Tool component is installed and used for universe creation
-
Check network traffic configuration for IDTInspect the network communication settings between the Information Design Tool client and the SAP BusinessObjects CMS server. Verify whether SSL/TLS encryption is enabled for the connection layer used by IDT.Affected if Network communications from IDT to the CMS are not encrypted (cleartext)
-
Inspect SSL/TLS configuration in CMCAccess the Central Management Console (CMC) and navigate to the Server Categories or Communication layer settings. Check the SSL configuration status for the CMS server and related services that handle IDT connections.Affected if SSL is disabled or not configured for the CMS and IDT communication channels
A user is affected if they run SAP BusinessObjects Platform version 4.20 or 4.30 with the Information Design Tool component and have not enabled TLS/SSL encryption for network communications.
Generated from the published advisory. Verify against your own configuration.
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 dataEnable TLS/SSL encryption for SAP BusinessObjects network communications, particularly for the Information Design Tool component. Configure secure communication channels and ensure all sensitive data transmission is encrypted.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28764 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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