CVE-2017-5002
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 Archer 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1 is affected by an open redirect vulnerability. A remote unprivileged attacker may potentially redirect legitimate users to arbitrary web sites and conduct phishing attacks. The attacker could then steal the victims' credentials and silently authenticate them to the RSA Archer application without the victims realizing an attack occurred.
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 confidenceOpen redirect vulnerability in EMC RSA Archer web application versions 5.4.1.3 through 5.5.3.1. Remote unauthenticated attackers can craft malicious URLs that redirect authenticated users to arbitrary external websites, enabling credential theft phishing attacks with silent re-authentication to the RSA Archer platform.
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= 5.4.1.3= 5.5.1.1= 5.5.1.3.1= 5.5.2= 5.5.2.3= 5.5.3.1CVSS 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.
-
Identify RSA Archer versionAccess the RSA Archer platform administration area or check the installation directory for version information. Common paths include the About page in the web interface or the installer logs.Affected if The installed version matches 5.4.1.3, 5.5.1.1, 5.5.1.3.1, 5.5.2, 5.5.2.3, or 5.5.3.1
-
Confirm web interface is exposedVerify the RSA Archer web application is accessible over HTTP/HTTPS. Check if the login page loads at the expected URL (typically /RSAArcher or similar endpoint).Affected if The web interface is externally or internally accessible and the version is in the affected list
-
Verify authentication is configuredConfirm that user authentication is enabled for the RSA Archer platform and users can log in to the web application.Affected if Users authenticate to the web application and the version is affected - the open redirect can then phish authenticated session credentials
-
Test redirect parameter behaviorSubmit a test request with an external URL in any redirect-capable parameter (such as returnUrl, redirect, or similar). Observe if the application redirects to the supplied external domain without validation.Affected if The application accepts and follows redirects to arbitrary external domains without validating against an allowlist
A user is affected if their RSA Archer EGRC installation version is 5.4.1.3, 5.5.1.1, 5.5.1.3.1, 5.5.2, 5.5.2.3, or 5.5.3.1 and the web interface is accessible to authenticated users.
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 vendor-provided security patches for affected RSA Archer versions; implement URL allowlist validation at the application or reverse proxy layer as a compensating control if immediate patching is not feasible.
- Consultation3.0 h
- Implementation8.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 $5,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5002 — 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-5002 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