CVE-2019-0268
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 Business Intelligence Platform (CMC Module), versions 4.10, 4.20 and 4.30, does not sufficiently validate an XML document accepted from an untrusted source.
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 · high confidenceXML External Entity (XXE) injection vulnerability in the Central Management Console (CMC) module of SAP BusinessObjects BI Platform. The application accepts XML documents from untrusted sources without proper validation, allowing attackers to exploit the XML parser to read internal files, perform Server-Side Request Forgery (SSRF), or cause denial of service.
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.1= 4.2= 4.3CVSS 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
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP BusinessObjects BI Platform installationLocate the BusinessObjects installation directory or check system services for 'SAP BusinessObjects' or 'BOE' processes. On Windows, common paths are C:\Program Files\SAP BusinessObjects or C:\Program Files (x86)\SAP BusinessObjects. On Linux/Unix, check /opt/sap_businessobjects/Affected if BusinessObjects BI Platform is not installed on the system
-
Identify the installed BusinessObjects versionCheck the version using the Central Configuration Manager (CCM) or look for versionInfo.properties in the installation directory. You can also access the CMC welcome page which typically displays the version number.Affected if The installed version is 4.1, 4.2, or 4.3 (or any version within these major release lines)
-
Verify Central Management Console (CMC) is accessibleAccess the CMC web interface by navigating to http(s)://<server>:8080/CMC or http(s)://<server>:8080/BOE/CMC (port may vary based on configuration). Check if the CMC login page loads.Affected if CMC is accessible without authentication or with low-privilege user credentials
-
Confirm XML input is accepted by CMCIdentify CMC features that accept XML input, such as import/export functions, report templates, or web service configurations within the CMC module. Test whether XML documents can be submitted through these interfaces.Affected if CMC accepts XML content from users without visible XML validation or entity processing restrictions
If SAP BusinessObjects BI Platform versions 4.1, 4.2, or 4.3 are installed AND the CMC module is accessible and accepts XML input, the environment is likely affected by CVE-2019-0268.
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 dataApply vendor-supplied SAP security patches for CVE-2019-0268. Alternatively, disable external entity processing and DTD processing in XML parsers used by the CMC module, and implement strict input validation for all XML content.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0268 — 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-2019-0268 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