dbcve.org
ArcherApplication · Rsa

CVE-2022-30585

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 6.9.3.4 / 6.10.0.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The REST API in Archer Platform 6.x before 6.11 (6.11.0.0) contains an Authorization Bypass Vulnerability. A remote authenticated malicious user could potentially exploit this vulnerability to view sensitive information. 6.10 P3 (6.10.0.3) and 6.9 SP3 P4 (6.9.3.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

The REST API in RSA Archer Platform versions 6.x before 6.11 contains an authorization bypass vulnerability. An authenticated remote user can exploit this to access sensitive information beyond their intended permissions by circumventing authorization checks in API endpoints.

MitigationUpgrade to Archer Platform version 6.11 (6.11.0.0), 6.10 P3 (6.10.0.3), or 6.9 SP3 P4 (6.9.3.4) as appropriate for your environment.

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, < 6.9.3.4>= 6.10.0.0, < 6.10.0.3

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installation
    Check for RSA Archer installation by looking for the default install directory (typically C:\Program Files\RSA Archer or /opt/rsa-archer) or by querying for the Archer web service running on IIS.
    Affected if RSA Archer Platform is not installed on the system.
  2. Identify installed Archer version
    Check the Archer version by reviewing the InstallInfo.xml file located in the Archer installation directory (commonly in \RSA Archer\Platform\ or \Instances\), or access the Archer About page via the web interface.
    Affected if The version falls within the affected ranges: 6.3 to 6.9.3.3, or 6.10.0.0 to 6.10.0.2.
  3. Verify REST API accessibility
    Confirm the REST API endpoint is exposed by accessing the Archer web URL followed by /api (e.g., https://your-archer-server/archer/api). Check if the API responds to unauthenticated or authenticated requests.
    Affected if The REST API is publicly or internally accessible over the network.
  4. Review user role assignments
    Examine the user accounts and roles configured in Archer via the Administration > Users > Users/_roles pages to identify which users have API access.
    Affected if Multiple user accounts with varying permission levels exist in the system.

You are affected if RSA Archer Platform is installed with a version between 6.3 and 6.9.3.3 or between 6.10.0.0 and 6.10.0.2, and the REST API is accessible to authenticated users.

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.9.3.4 / 6.10.0.3 or later
Fixed in 6.9.3.46.10.0.3
Interim mitigation

Upgrade to Archer Platform version 6.11 (6.11.0.0), 6.10 P3 (6.10.0.3), or 6.9 SP3 P4 (6.9.3.4) as appropriate for your environment.

Recommended fix High confidence

Upgrade to 6.9.3.4, 6.10.0.3, or 6.11.0.0 or later

  1. 1. Identify the current installed version of Archer Platform by checking the About page or system information
  2. 2. Determine the appropriate upgrade path based on your current version (6.9.x should upgrade to 6.9.3.4+, 6.10.x should upgrade to 6.10.0.3+, or upgrade to 6.11.0.0+)
  3. 3. Review Archer upgrade documentation and release notes for the target version
  4. 4. Create a complete backup of the Archer database and configuration files
  5. 5. Test the upgrade in a non-production/staging environment first
  6. 6. Schedule a maintenance window for the production upgrade
  7. 7. Perform the upgrade following the official Archer installation/upgrade guide
  8. 8. Verify the upgrade completed successfully by checking the version
Caveat Review release notes for breaking changes; major version upgrades may introduce behavioral changes requiring testing

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

Fix this in Archer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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