CVE-2020-5336
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 injection vulnerability. An unauthenticated attacker could potentially exploit this vulnerability by tricking a victim application user to execute malicious JavaScript code on 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 · high confidenceRSA Archer versions before 6.7 P1 contain a URL injection vulnerability that allows an unauthenticated attacker to inject malicious JavaScript code via crafted URLs, tricking authenticated users into executing the payload in their browser context.
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 installed RSA Archer versionLog into the RSA Archer web interface and navigate to the About page or System Information section, typically found under Administration or System Settings. Alternatively, check the installation directory for version files or the archer version in the control panel if installed as a Windows service.Affected if The displayed version number is less than 6.7.0.1 (for example, 6.7.0.0, 6.6.x, or earlier)
-
Confirm version is within vulnerable rangeCompare the identified version against the affected range. RSA Archer versions prior to 6.7.0.1 are vulnerable.Affected if The version starts with 6.7.0.0 or any earlier release (6.6.x, 6.5.x, etc.)
-
Verify this is a web-facing deploymentDetermine if the RSA Archer instance is accessible over HTTP/HTTPS to unauthenticated attackers who could craft malicious URLs. Check network exposure settings and IIS or web server configuration.Affected if The application is accessible to unauthenticated users on the network or internet
-
Assess if users would click external URLsEvaluate whether authenticated users in the environment might click on links from external sources (email, chat, documents) that could contain crafted malicious URLs pointing to the Archer instance.Affected if Users routinely access external links and the application is exposed as described above
A user is affected if their installed RSA Archer version is below 6.7.0.1 and the web interface is accessible to unauthenticated attackers who could trick authenticated users into clicking malicious crafted URLs.
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
Upgrade RSA Archer to version 6.7 P1 (6.7.0.1) or later to remediate this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5336 — 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-5336 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