CVE-2017-8913
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 · uneditedThe Visual Composer VC70RUNTIME component in SAP NetWeaver AS JAVA 7.5 allows remote authenticated users to conduct XML External Entity (XXE) attacks via a crafted XML document in a request to irj/servlet/prt/portal/prtroot/com.sap.visualcomposer.BIKit.default, aka SAP Security Note 2386873.
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 confidenceThe Visual Composer VC70RUNTIME component in SAP NetWeaver AS JAVA 7.5 is vulnerable to XML External Entity (XXE) injection. Remote authenticated attackers can exploit this by submitting crafted XML documents to the irj/servlet/prt/portal/prtroot/com.sap.visualcomposer.BIKit.default endpoint, potentially reading internal files, performing SSRF, or causing 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= 7.50CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS Java versionUse SAP transaction code SM51 or check the SAP system version banner to confirm the NetWeaver Java release version. Compare your installed version against the affected range: version 7.50.Affected if The installed version is exactly 7.50 (SAP NetWeaver AS Java 7.5)
-
Confirm Visual Composer component is installedCheck the SAP system for presence of the Visual Composer (VC) component. In SAP NetWeaver Administrator, navigate to Systems -> Services -> Components or use the SAP Management Console to list installed components.Affected if Visual Composer component is installed and present in the SAP system
-
Verify the vulnerable endpoint is accessibleAttempt to access the URL pattern /irj/servlet/prt/portal/prtroot/com.sap.visualcomposer.BIKit.default through the SAP portal. This may require authentication depending on portal configuration.Affected if The Visual Composer endpoint responds (even with authentication required, the endpoint exists and is reachable)
-
Check if XML-based requests are acceptedSubmit a test XML payload (such as a simple well-formed XML document) to the vulnerable endpoint using an HTTP client. Observe if the server processes and accepts XML input without rejecting it.Affected if The endpoint accepts and processes XML requests, indicating the XXE attack surface is present
If running SAP NetWeaver AS Java version 7.50 with Visual Composer installed and the /irj/servlet/prt/portal/prtroot/com.sap.visualcomposer.BIKit.default endpoint accessible, the environment is affected by this XXE vulnerability.
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 SAP Security Note 2386873 which provides the patch for this XXE vulnerability. Prior to patching, consider restricting access to the Visual Composer component or disabling it if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8913 — 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-2017-8913 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