dbcve.org
ArcherApplication · Archerirm

CVE-2024-34090

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. The login banner in the Archer Control Panel (ACP) did not previously escape content appropriately. 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 exists in the Archer Platform login banner within the Archer Control Panel (ACP). The banner content is not properly escaped, allowing an authenticated attacker with banner configuration privileges to inject malicious JavaScript that executes in the browsers of all users viewing the login page.

MitigationUpgrade Archer Platform to version 2024.04 or 6.14 P3 (6.14.0.3) which contain the fix for proper content escaping in the login banner.

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 the installed Archer version
    Access the Archer Control Panel (ACP) and navigate to About or System Settings to find the installed version number. Alternatively, check the installation documentation or the version displayed in the ACP login page footer.
    Affected if The installed version is either 2024.03 or lower than 6.14.0.3 (for example, 6.13.x, 6.12.x, etc.)
  2. Verify if the login banner feature is configured
    Log into the Archer Control Panel with administrative privileges. Navigate to Banner Configuration or similar settings under System Administration or Security Settings to determine whether a login banner has been enabled.
    Affected if A login banner is currently enabled and configured with custom content
  3. Inspect the banner content for unescaped characters
    View the banner text or HTML content in the banner configuration screen. Look for any raw script tags, unescaped HTML elements, or JavaScript event handlers that may not have been properly sanitized.
    Affected if The banner contains unsanitized HTML tags, script elements, or JavaScript event handlers that could execute in a user's browser
  4. Confirm user privileges in the environment
    Review user accounts that have banner configuration or ACP administrative privileges. Determine if any accounts with these permissions exist or could be compromised.
    Affected if There are users with banner configuration privileges, making the stored XSS exploitable if banner content is modified

Your environment is affected if you are running Archer version 2024.03 or any version lower than 6.14.0.3 AND the login banner feature is currently enabled in your Archer Control Panel.

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 Archer Platform to version 2024.04 or 6.14 P3 (6.14.0.3) which contain the fix for proper content escaping in the login banner.

Recommended fix High confidence

6.14 P3 (6.14.0.3) or 2024.04+

  1. Confirm current Archer Platform version is < 6.14.0.3 or = 2024.03 by checking Archer Control Panel (ACP) or system information
  2. Create a complete backup of the Archer database and application files
  3. Schedule a maintenance window for the upgrade
  4. Download the fixed release: 6.14 P3 (6.14.0.3) or 2024.04 from the RSA Archer download portal
  5. Follow the standard Archer upgrade documentation to install the fixed release
  6. After upgrade, verify the login banner functionality works correctly
  7. Verify the fix by checking that content in the login banner is now properly escaped/sanitized
Caveat Review Archer release notes for any configuration or compatibility changes between your version and the target release

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

Fix this in Archer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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