CVE-2017-14373
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 · uneditedEMC RSA Authentication Manager 8.2 SP1 P4 and earlier contains a reflected cross-site scripting vulnerability that could potentially be exploited by malicious users to compromise the affected system.
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 confidenceReflected cross-site scripting (XSS) vulnerability in EMC RSA Authentication Manager 8.2 SP1 P4 and earlier. The vulnerability allows attackers to inject malicious JavaScript code through crafted URLs that are reflected back to users without proper sanitization, potentially enabling session hijacking, credential theft, or arbitrary actions in the context of the victim's session.
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<= 8.2CVSS 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 Authentication Manager is installedIdentify if EMC RSA Authentication Manager is running in your environment by checking for the application on typical web ports (default HTTPS ports 443, 8443) or by looking for the RSA AM process/serviceAffected if The application is present in your environment
-
Check installed version numberAccess the RSA Authentication Manager administrator console and navigate to the About or System Information page to view the exact version and patch level installedAffected if The version is 8.2 SP1 P4 or earlier, or any version <= 8.2
-
Identify the affected web endpointExamine the RSA Authentication Manager login page and surrounding web URLs for parameters that accept user input and reflect it back in the response. Look for query parameters in URLs that are directly displayed in the page without encodingAffected if User-supplied input in URL parameters is reflected in the response without sanitization
-
Test for XSS vulnerability existenceUsing a controlled test, append a benign XSS probe string (such as a simple script alert) to suspected URL parameters and observe whether the payload is reflected back as-is in the HTML response rather than being encoded or strippedAffected if The crafted payload is reflected directly in the page source without HTML encoding
You are affected if RSA Authentication Manager version 8.2 or earlier is installed and the web interface reflects URL parameters without sanitization, allowing injected script content to appear in the response.
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 the vendor security patch or upgrade to a version newer than RSA Authentication Manager 8.2 SP1 P4. Alternatively, implement input validation and output encoding on the affected endpoints to neutralize malicious script payloads.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14373 — 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-14373 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