dbcve.org
ArcherApplication · Rsa

CVE-2022-37317

MEDIUM · 5.4 CVSS v3.1 Published 2022-08-25
Fix available
A fix is available. Upgrade to 6.10.0.4 / 6.11.0.2.4 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
Archer Platform 6.x before 6.11 P3 contain an HTML injection vulnerability. An authenticated remote attacker could potentially exploit this vulnerability by tricking a victim application user to execute malicious code in the context of the web application. 6.10 P4 (6.10.0.4) and 6.11 P2 HF4 (6.11.0.2.4) are also fixed releases.

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

HTML injection vulnerability in RSA Archer Platform versions 6.x before 6.11 P3 allows authenticated remote attackers to inject malicious HTML/JavaScript code that executes in the context of victim users' web sessions, potentially leading to session hijacking or credential theft.

MitigationApply vendor patches by upgrading to version 6.11 P3, 6.10 P4 (6.10.0.4), or 6.11 P2 HF4 (6.11.0.2.4) as specified in the advisory.

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.0, < 6.10.0.4>= 6.11, < 6.11.0.2.4

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. Confirm RSA Archer Platform is present
    Identify if RSA Archer web application is running in your environment by checking for web servers hosting the Archer application (typically accessible on standard web ports).
    Affected if RSA Archer Platform is installed and accessible via web interface.
  2. Locate the installed version number
    Log into the RSA Archer web interface as an administrator and navigate to the About or System Settings page to view the version. Alternatively, check installation or configuration files for the version metadata.
    Affected if The exact version number is visible in the application.
  3. Compare version against affected range one
    Check if installed version is >= 6.0.0.0 and < 6.10.0.4. This includes versions 6.0.x through 6.9.x and 6.10.0.0 through 6.10.0.3.
    Affected if Installed version falls within 6.0.0.0 <= version < 6.10.0.4.
  4. Compare version against affected range two
    Check if installed version is >= 6.11.0.0 and < 6.11.0.2.4. This includes versions 6.11.0.0 through 6.11.0.2.3.
    Affected if Installed version falls within 6.11.0.0 <= version < 6.11.0.2.4.
  5. Confirm authentication is enabled
    Verify that user authentication is required to access the Archer web interface. The vulnerability requires an authenticated attacker to inject the malicious code.
    Affected if The application accepts user credentials and maintains authenticated sessions.

You are affected if your RSA Archer Platform version is 6.0.x through 6.10.0.3, or 6.11.0.0 through 6.11.0.2.3, and the web interface with authentication is enabled.

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.10.0.4 / 6.11.0.2.4 or later
Fixed in 6.10.0.46.11.0.2.4
Interim mitigation

Apply vendor patches by upgrading to version 6.11 P3, 6.10 P4 (6.10.0.4), or 6.11 P2 HF4 (6.11.0.2.4) as specified in the advisory.

Recommended fix High confidence

6.10.0.4 or 6.11.0.2.4

  1. Identify the currently installed Archer Platform version
  2. If running version 6.0 through 6.10.0.3, upgrade to 6.10.0.4 (6.10 P4)
  3. If running version 6.11 through 6.11.0.2.3, upgrade to 6.11.0.2.4 (6.11 P2 HF4)
  4. After upgrading, test the application to confirm the HTML injection vulnerability is remediated
  5. Apply the upgrade in a non-production environment first to validate compatibility with existing configurations and integrations

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

Fix this in Archer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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