dbcve.org
ArcherApplication · Archerirm

CVE-2024-34089

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 6.14.0.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
An issue was discovered in Archer Platform 6 before 2024.04. There is a stored cross-site scripting (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 victim users access the data store through their browsers, the malicious code gets executed by the web browser in the context of the vulnerable application. 6.14 P3 (6.14.0.3) is also a fixed release.

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 confidence

A stored cross-site scripting (XSS) vulnerability in RSA Archer Platform versions before 2024.04 allows authenticated malicious users to inject malicious HTML or JavaScript code into a trusted application data store. When other users access this data through their browsers, the injected code executes in the context of the vulnerable application.

MitigationUpgrade to Archer Platform 2024.04 or 6.14 P3 (6.14.0.3) which contain the fix. Until then, implement input validation and output encoding on data stored in the application and consider restricting permissions for untrusted users.

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
ArcherApplication
Affected:< 6.14.0.3= 2024.03

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Archer Platform version
    Access the Archer Platform through the web interface and navigate to About/Version information, or check the installation directory for version metadata files if you have server access. The version is typically displayed on the login page footer or in the Administration > System > Overview section.
    Affected if The version displayed is lower than 6.14.0.3 OR equals exactly 2024.03. These specific versions contain the vulnerability.
  2. Confirm active user authentication is possible
    Verify that the Archer Platform login page is accessible and users can authenticate. The vulnerability requires an authenticated user to inject malicious script, so the presence of working authentication indicates the attack surface exists.
    Affected if Users can log in successfully to the Archer Platform - the XSS can only be exploited by authenticated users.
  3. Check if application is accessible to browsers
    Confirm the Archer Platform web interface loads in a browser. The stored XSS executes when other users access the injected data through their browsers, so browser-accessible web interfaces are required.
    Affected if The Archer Platform web application is reachable via HTTP/HTTPS in a web browser - this is the delivery mechanism for the exploit.
  4. Verify user account existence
    Review user accounts in the Archer Platform Administration panel under User Management. The attacker needs a valid user account to inject the malicious script.
    Affected if There are one or more user accounts configured in the system. The vulnerability requires an authenticated (malicious) user to inject the payload.

You are affected if your installed Archer Platform version is 2024.03 or any version lower than 6.14.0.3, and the web application is accessible to authenticated users who can input data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 6.14.0.3 or later
Fixed in 6.14.0.3
Interim mitigation

Upgrade to Archer Platform 2024.04 or 6.14 P3 (6.14.0.3) which contain the fix. Until then, implement input validation and output encoding on data stored in the application and consider restricting permissions for untrusted users.

Recommended fix High confidence

Upgrade to Archer Platform 6.14 P3 (6.14.0.3) or 2024.04 and later

  1. Download the 6.14 P3 (6.14.0.3) or later upgrade package from the RSA Archer Support Portal
  2. Review the Archer Platform upgrade guide for version-specific upgrade procedures
  3. Back up the existing Archer database and configuration files
  4. Test the upgrade in a non-production environment before deploying to production
  5. Execute the upgrade following the documented upgrade path for your current version
  6. Verify the installation by logging in and confirming all components function correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34089 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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