CVE-2017-14372
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 · uneditedRSA Archer GRC Platform prior to 6.2.0.5 is affected by reflected cross-site scripting vulnerabilities via certain RSA Archer Help pages. Attackers could potentially exploit this to execute arbitrary HTML in the user's browser session in the context of the affected RSA Archer application.
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 confidenceThis is a reflected cross-site scripting (XSS) vulnerability in RSA Archer GRC Platform affecting help pages prior to version 6.2.0.5. Attackers can craft malicious URLs containing arbitrary HTML/JavaScript that gets reflected and executed in the victim's browser session when they access certain help pages.
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<= 6.2.0.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.
-
Confirm RSA Archer GRC Platform is installedCheck for the application in your system by looking for the RSA Archer installation directory, IIS website, or Windows service named 'Archer' or 'RSA Archer'Affected if RSA Archer GRC Platform is not found in your environment, you are not affected
-
Identify the installed version of RSA Archer GRC PlatformAccess the RSA Archer About page (typically /ArcherTech/About.aspx via the web interface) or check the version information in the installation directoryAffected if The installed version is 6.2.0.4 or any earlier version (6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2.0.0, etc.)
-
Verify the help pages are accessibleTry accessing the help documentation pages through the RSA Archer web interface, typically found under the Help menu or /ArcherTech/help/ pathAffected if Help pages are disabled or inaccessible in your environment, the attack surface may be reduced
-
Check for the vulnerable help page URL patternExamine URL parameters when accessing help pages - look for query string parameters that might reflect user input without proper encoding. Test by attempting a benign XSS probe in the URL (e.g., ?topic=<script>alert(1)</script>)Affected if The help page URLs reflect unsanitized input from the query string back to the page response
You are affected if RSA Archer GRC Platform is installed and the version is 6.2.0.4 or earlier, with help pages accessible and URL parameters reflecting unencoded 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 dataUpgrade to RSA Archer GRC Platform 6.2.0.5 or later which contains the fix for this vulnerability. As a compensating control, implement input validation and output encoding on help page parameters.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14372 — 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-14372 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