dbcve.org
ArcherApplication · Archerirm

CVE-2024-34091

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 in the background of the application and renders content inaccessible. 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 prior to 2024.04 allows authenticated users to inject malicious HTML or JavaScript code into a trusted application data store. When other users access this data store through their browsers, the malicious code executes in the background, causing content inaccessibility.

MitigationUpgrade RSA Archer Platform to version 2024.04 or patch level 6.14.0.3 (6.14 P3) to remediate this vulnerability.

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 RSA Archer Platform installation
    Check if RSA Archer Platform is installed in your environment by looking for the Archer web application directory or checking for the RSA Archer web interface URL.
    Affected if RSA Archer Platform is not installed
  2. Determine installed RSA Archer version
    Access the Archer web interface and navigate to About or the Control Panel to view the build version. Alternatively, check the installation logs or registry for the exact version number.
    Affected if Version cannot be determined or is not visible
  3. Compare version against affected ranges
    Check if the installed version is either: (1) less than 6.14.0.3, or (2) exactly 2024.03. Note that versions 6.14.0.3 (6.14 P3) and 2024.04 are not affected.
    Affected if Installed version is < 6.14.0.3 or equals 2024.03
  4. Confirm user authentication is enabled
    Verify that user authentication is enabled in the Archer Platform, as the vulnerability requires authenticated users to inject the malicious code.
    Affected if Authentication is disabled (though this is unlikely in production)
  5. Identify accessible application data stores
    Check which application data stores the web interface exposes. These are the potential vectors where malicious script could be stored.
    Affected if Application data stores are accessible through the web interface

You are affected if your RSA Archer Platform version is less than 6.14.0.3 or exactly 2024.03, and you have authenticated users accessing application data stores through the web interface.

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 RSA Archer Platform to version 2024.04 or patch level 6.14.0.3 (6.14 P3) to remediate this vulnerability.

Recommended fix High confidence

6.14 P3 (6.14.0.3) or 2024.04

  1. Identify current Archer Platform version by navigating to System Administration > System Settings > About
  2. Review Archer upgrade documentation and release notes for version 6.14.0.3 or 2024.04
  3. Create a full backup of the Archer database and configuration files
  4. Set up a staging environment matching production configuration
  5. Test the upgrade in the staging environment to validate functionality and identify any regressions
  6. Schedule a maintenance window for the production upgrade
  7. Perform the upgrade to version 6.14.0.3 (6.14 P3) or 2024.04
  8. After upgrade, verify the XSS fix by confirming the vulnerability is no longer present
Caveat Review release notes for any configuration or workflow changes; standard upgrade testing recommended

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

Fix this in Archer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34091 — 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-34091 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