ArcherApplication · Archerirm

CVE-2024-49210

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-22
Fix available
A fix is available. Upgrade to 2024.09 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected XSS was discovered in an iView List Archer Platform UX page in Archer Platform 6.x before version 2024.09. A remote unauthenticated attacker could potentially exploit this by tricking a victim application user into supplying malicious HTML or JavaScript code to the vulnerable web application; the malicious code is then reflected back to the victim and 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 confidence

Reflected XSS vulnerability in the iView List page of RSA Archer Platform 6.x allows an unauthenticated remote attacker to inject malicious HTML or JavaScript code through user input that gets reflected back to the victim and executed in their browser context.

MitigationUpgrade to Archer Platform version 2024.09 or later which contains the security patch for 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.3.0.0, < 2024.09

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

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

  1. Determine RSA Archer Platform version
    Locate the Archer Platform installation and check the version information, typically found in the installation directory, about page, or system information within the Archer control panel. Compare the installed version against the affected range of >= 6.3.0.0 and < 2024.09.
    Affected if The installed version is 6.3.0.0 or higher but lower than 2024.09
  2. Identify if iView List page component is present
    Access the Archer Platform web interface and navigate to the iView List functionality. This is typically found in the navigation menu under iViews or through direct URL access to the iView List endpoint.
    Affected if The iView List page is accessible without authentication or with valid user credentials
  3. Verify user input handling in iView List
    Inspect the iView List page for any input fields, search parameters, or URL parameters that accept user-supplied data and display results back to the user.
    Affected if User-supplied input in the iView List page is reflected back in the response without proper output encoding or sanitization

The environment is affected if RSA Archer Platform version is 6.3.0.0 or higher but lower than 2024.09 AND the iView List page component is accessible and reflects user input without sanitization.

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.09 or later
Fixed in 2024.09
Interim mitigation

Upgrade to Archer Platform version 2024.09 or later which contains the security patch for this vulnerability.

Recommended fix High confidence

2024.09 or later

  1. Upgrade Archer Platform to version 2024.09 or later to resolve the reflected XSS vulnerability in the iView List UX page
  2. After upgrading, verify the fix by testing the iView List functionality with input validation to confirm malicious scripts are properly sanitized
  3. Review release notes for version 2024.09 for any additional security updates or changes

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-49210 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49210 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