CVE-2020-29537
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 · uneditedArcher before 6.8 P2 (6.8.0.2) is affected by an open redirect vulnerability. A remote privileged 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 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 confidenceArcher before version 6.8 P2 (6.8.0.2) contains an open redirect vulnerability that allows a remote privileged attacker to manipulate URL parameters to redirect users to arbitrary external websites. This enables phishing attacks where victims can be tricked into visiting malicious sites while believing they remain within the legitimate Archer application.
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.6, < 6.6.0.8>= 6.7, < 6.7.0.8>= 6.8, < 6.8.0.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine installed Archer versionLog into the Archer web interface and navigate to About or look at the footer of the login page. Alternatively, check the installation directory for version information or query the Windows Registry under HKLM\SOFTWARE\RSA\Archer for the installed version key.Affected if The version falls within these ranges: 6.6.0.0 to 6.6.0.7, 6.7.0.0 to 6.7.0.7, or 6.8.0.0 to 6.8.0.1.
-
Identify if web interface is accessibleVerify that the Archer web application is reachable and functional by accessing the login URL.Affected if The web interface is exposed and accepts URL parameters for redirection.
-
Check for URL redirect parameter handlingReview web server logs or use a browser to test whether URL parameters controlling redirection (such as 'returnUrl', 'redirect', or 'url' parameters) are processed by the application without proper validation.Affected if The application accepts and follows redirect parameters without validating that the target domain is internal.
You are affected if your installed Archer version is 6.6.0.0 through 6.6.0.7, 6.7.0.0 through 6.7.0.7, or 6.8.0.0 through 6.8.0.1 and the web interface is accessible, allowing URL redirect parameters to be processed without domain validation.
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.6.0.86.7.0.86.8.0.2
Upgrade Archer to version 6.8 P2 (6.8.0.2) or later to resolve the open redirect vulnerability. Additionally, implement URL validation to ensure redirect parameters only allow trusted domains.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-29537 — 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-29537 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