CVE-2020-5337
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, versions prior to 6.7 P1 (6.7.0.1), contain a URL redirection vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability to redirect application users to arbitrary web URLs by tricking the victim users to click on maliciously crafted links. The vulnerability could be used to conduct phishing attacks that cause users to unknowingly visit malicious sites.
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 confidenceRSA Archer versions prior to 6.7 P1 (6.7.0.1) contain an open redirect vulnerability that allows a remote unauthenticated attacker to craft malicious URLs redirecting users to arbitrary websites. This is achieved by tricking victims into clicking specially crafted links within the application, enabling phishing attacks.
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.7.0.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.1/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 installation versionNavigate to the RSA Archer application about page (typically /Archer/about.aspx) or access the System Administration > System Settings > General page to view the installed version numberAffected if The displayed version is less than 6.7.0.1 (for example, 6.7.0.0, 6.6.x, or earlier)
-
Verify version through system informationAccess the RSA Archer System Administration menu and locate the System Information or Installation Details section which displays the exact build version and patch levelAffected if The version shown is a build prior to 6.7.0.1 or shows no patch level (P1)
-
Check for URL redirect functionalityExamine application URLs for parameters that handle redirection such as 'ReturnUrl', 'redirect', 'url', or 'dest' parameters commonly used in login and navigation linksAffected if Such redirect parameters exist and accept external domain values without validation
-
Review web server logs for suspicious redirect patternsInspect IIS or application logs for incoming requests with redirect parameters containing external domains (for example, URLs containing 'http://' or 'https://' in redirect parameter values)Affected if Unauthenticated requests with external redirect targets are present in the logs
You are affected if your installed RSA Archer version is any build earlier than 6.7.0.1 and the application uses URL redirect parameters accessible to unauthenticated 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 data6.7.0.1
Apply vendor patch 6.7 P1 (6.7.0.1) or later to remediate the URL redirection vulnerability. Additionally, implement URL validation and warn users when navigating to external domains.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5337 — 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-2020-5337 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