CVE-2020-29535
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 P4 (6.8.0.4) contains a stored XSS vulnerability. A remote authenticated malicious Archer user could potentially exploit this vulnerability to store malicious HTML or JavaScript code in a trusted application data store. When application users access the corrupted data store through their browsers, the malicious code gets executed by the web browser in the context of the vulnerable web application.
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 confidenceThis is a stored (persistent) cross-site scripting (XSS) vulnerability in RSA Archer platform versions before 6.8 P4 (6.8.0.4). An authenticated malicious user can inject arbitrary HTML or JavaScript code into a trusted application data store. When other users access the compromised data through their browsers, the malicious payload executes in the context of the vulnerable web application, potentially allowing session hijacking, credential theft, or defacement.
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.5>= 6.9, < 6.9.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
- 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.
-
Identify installed RSA Archer versionLog into the RSA Archer web interface as an administrator and navigate to the About page (typically under Administration > System > About) or check the version displayed on the login page. Alternatively, inspect the installation directory for version files or check the system information page.Affected if The version displayed is any of the following: 6.6.x where x < 8; 6.7.x where x < 8; 6.8.x where x < 5; 6.9.x where x < 1
-
Confirm the build number matches vulnerable releasesLocate the full build number or patch level in the system information. The affected versions are: 6.6.0.0 through 6.6.0.7, 6.7.0.0 through 6.7.0.7, 6.8.0.0 through 6.8.0.4, or 6.9.0.0.Affected if The build number is lower than 6.6.0.8, 6.7.0.8, 6.8.0.5, or 6.9.0.1 respectively for your major version line
-
Verify user-accessible application data entry existsCheck if any custom or standard RSA Archer applications are configured to accept user-submitted data through forms, questionnaires, or data entry fields that are accessible to authenticated users.Affected if One or more applications contain data entry fields that accept free-text input from users
-
Confirm authentication mechanisms allow user accessVerify that non-administrator users have access to create or modify records in any application that stores user-supplied data.Affected if Standard or custom user roles have permissions to add or edit records in applications that store input data
You are affected if your RSA Archer installation version falls within the vulnerable ranges (6.6.x < 6.6.0.8, 6.7.x < 6.7.0.8, 6.8.x < 6.8.0.5, or 6.9.x < 6.9.0.1) and users can submit data to application fields.
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.5
Apply the vendor patch (6.8 P4 / 6.8.0.4 or later) to remediate this vulnerability. Additionally, implement output encoding and input validation for all user-supplied data submitted to application data stores as a defense-in-depth measure.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-29535 — 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-29535 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