dbcve.org
ArcherApplication · Archerirm

CVE-2024-41707

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-25
Fix available
A fix is available. Upgrade to 2024.06 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.06. Authenticated users can achieve HTML content injection. A remote authenticated malicious Archer user could potentially exploit this to store malicious HTML 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.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in RSA Archer Platform versions prior to 2024.06. Authenticated users can inject malicious HTML/JavaScript code into application data stores. When other users access this data through their browsers, the injected code executes in the context of the trusted Archer application.

MitigationUpgrade to Archer Platform 2024.06 or later to receive the vendor patch. Additionally, implement proper input validation and output encoding for all user-supplied data before rendering in browsers.

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:< 2024.06

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. Verify the installed RSA Archer Platform version
    Access the Archer web interface and navigate to Administration > System > General Settings, or check the About section in the application. Alternatively, consult your installation documentation or software inventory for the deployed version number.
    Affected if The installed version is earlier than 2024.06 (for example, 6.x, 2023.x, or any release prior to the 2024.06 milestone).
  2. Confirm the Archer web application is accessible
    Attempt to access the Archer login page via the configured URL (typically https://hostname/Archer) using a web browser or curl command.
    Affected if The application is reachable and users authenticate to access it, making them potential targets for XSS execution.
  3. Review application data stores for suspicious script content
    Use the Archer search functionality or database queries to examine fields that accept user input (such as questionnaire responses, custom objects, or metadata fields) for patterns like <script>, javascript:, onerror=, or other HTML/JS injection vectors.
    Affected if Stored data contains unsanitized HTML or JavaScript code that could execute when viewed by other users.
  4. Examine Archer system and audit logs for XSS-related events
    Navigate to Archer Administration > Logging > View Logs, or access the Windows Event Viewer / syslog files if Archer logs are exported. Search for entries containing XSS-related keywords or unusual script tags in user input.
    Affected if Logs show evidence of XSS payloads being submitted or stored in the system.

You are affected if the deployed RSA Archer Platform version is earlier than 2024.06 and the application is accessible to authenticated users who can input data that gets rendered in browsers.

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 2024.06 or later
Fixed in 2024.06
Interim mitigation

Upgrade to Archer Platform 2024.06 or later to receive the vendor patch. Additionally, implement proper input validation and output encoding for all user-supplied data before rendering in browsers.

Recommended fix Moderate confidence

Archer Platform 2024.06

  1. Verify current Archer Platform version by accessing the About section in the Archer UI or checking the installation
  2. Review the Archer 2024.06 release notes for new features, resolved issues, and any known compatibility considerations
  3. Ensure you have a complete backup of the Archer database and configuration files before proceeding
  4. Schedule an appropriate maintenance window with stakeholders
  5. Download the Archer 2024.06 (or latest stable) installation package from the official RSA Customer Support portal or authorized distribution channel
  6. Follow the standard Archer upgrade documentation: run the installer, complete pre-upgrade checks, execute the upgrade, and verify post-upgrade system functionality
  7. After upgrade, verify the HTML content injection vulnerability is resolved by testing the affected data store functionality
Caveat Review release notes for any configuration or workflow changes that may require adjustment post-upgrade

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

Fix this in Archer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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