CVE-2017-11460
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 · uneditedCross-site scripting (XSS) vulnerability in the DataArchivingService servlet in SAP NetWeaver Portal 7.4 allows remote attackers to inject arbitrary web script or HTML via the responsecode parameter to shp/shp_result.jsp, aka SAP Security Note 2308535.
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 confidenceReflected cross-site scripting (XSS) vulnerability in SAP NetWeaver Portal 7.4's DataArchivingService servlet. The responsecode parameter in shp/shp_result.jsp fails to properly sanitize user input, allowing injection of arbitrary HTML or JavaScript that executes in the context of the victim's browser.
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.4CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 NetWeaver Portal versionAccess the SAP NetWeaver Administrator (NWA) or use transaction SM37, or check the installed product version via SAP LMDB. Look for the exact version number in the system information.Affected if The installed version is exactly 7.4 (no other versions are listed as affected)
-
Confirm DataArchivingService servlet presenceCheck if the DataArchivingService servlet is deployed on the system by examining the SAP application server's web container or deployment descriptors. Look for servlet mappings related to DataArchivingService.Affected if The DataArchivingService servlet is deployed and active on the portal
-
Locate the vulnerable JSP fileNavigate to the web application directory and verify the presence of shp/shp_result.jsp. On SAP NetWeaver, this is typically found under the portal's web content directory.Affected if The file shp/shp_result.jsp exists in the deployed web applications
-
Check servlet parameter accessibilityExamine the servlet configuration (web.xml or equivalent) to verify that the vulnerable endpoint accepts the responsecode parameter. This parameter is used in the shp_result.jsp file.Affected if The responsecode parameter is accepted by the servlet without validation filters
-
Confirm internet-facing exposureReview the SAP Internet Communication Manager (ICM) configuration and network settings to determine if the /shp/ path is exposed to untrusted networks or the internet.Affected if The vulnerable servlet is accessible from untrusted networks
A system is affected only if it is running SAP NetWeaver Portal version 7.4 with the DataArchivingService servlet and shp/shp_result.jsp file accessible, exposing the responsecode parameter to user input.
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 2308535 which patches the vulnerable servlet. Input validation and output encoding should be implemented on the responsecode parameter in shp/shp_result.jsp.
- 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-11460 — 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-11460 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