CVE-2017-14516
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) exists in SAP Business Objects Financial Consolidation before 2017-06-13, aka SAP Security Note 2422292.
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 confidenceCross-Site Scripting (XSS) vulnerability in SAP Business Objects Financial Consolidation allows attackers to inject malicious scripts through unsanitized user inputs. The vulnerability exists in versions prior to the June 2017 patch released via SAP Security Note 2422292. This is a reflected XSS issue that could allow session hijacking or credential theft when users access specially crafted URLs.
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 dataall versionsCVSS 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.
-
Locate SAP BusinessObjects Financial Consolidation installationIdentify the installation path or SAP system components for BusinessObjects Financial Consolidation. Check system information, installed programs list, or SAP LM structure for the Financial Consolidation module.Affected if The software is installed but version information is unavailable or shows pre-June 2017 release dates
-
Determine installed versionAccess the version information through SAP system details, about dialog, or version files within the BusinessObjects Financial Consolidation installation directory. Compare the version/build number to releases dated after 2017-06-13.Affected if Version shows as unpatched or cannot be confirmed as the June 2017 or later patched release
-
Verify SAP Security Note 2422292 statusCheck SAP system notes or patch management records to see if Security Note 2422292 has been applied to the environment.Affected if The security note is not listed as applied or the patch status is unknown
-
Assess web interface exposureDetermine if the SAP BusinessObjects Financial Consolidation web tier is accessible to users. Since this is a reflected XSS vulnerability exploited through specially crafted URLs, check if the web interface handles user-supplied input without sanitization.Affected if Web interface is exposed and the application handles URL parameters without confirmed patched validation
A user is affected if SAP BusinessObjects Financial Consolidation is installed with a version prior to the June 2017 patch and the web tier is accessible without verified application of Security Note 2422292.
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 2422292 by upgrading to the patched version of SAP Business Objects Financial Consolidation released after 2017-06-13, or implement input validation and output encoding as compensating controls if immediate patching is not feasible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14516 — 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-14516 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