dbcve.org
ArcherApplication · Rsa

CVE-2021-38362

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to 6.9.3.0.1 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
In RSA Archer 6.x through 6.9 SP3 (6.9.3.0), an authenticated attacker can make a GET request to a REST API endpoint that is vulnerable to an Insecure Direct Object Reference (IDOR) issue and retrieve sensitive data.

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

RSA Archer 6.x through 6.9 SP3 contains a REST API endpoint vulnerable to Insecure Direct Object Reference (IDOR). An authenticated attacker can manipulate object references in GET requests to access sensitive data they should not be authorized to view, due to missing or inadequate authorization validation on the endpoint.

MitigationImplement proper authorization checks on the REST API endpoint to verify the authenticated user has permission to access the requested object before returning data. Consider adding consistent object-level access control validation across all API endpoints.

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.1.0.0, < 6.9.3.0.1

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. Identify RSA Archer installed version
    Locate the RSA Archer installation directory and check the version information file, or use the Archer help About function within the application. Common locations include the installation root or within the Web directory.
    Affected if The installed version is >= 6.1.0.0 and < 6.9.3.0.1, meaning it falls within the vulnerable version range.
  2. Verify REST API is enabled
    Check the RSA Archer web.config or API configuration settings to confirm the REST API functionality is turned on. This is typically found in the IIS-hosted web application configuration.
    Affected if The REST API endpoint is accessible and enabled in the environment.
  3. Review API endpoint authorization configuration
    Examine the API authorization settings or custom module configuration files within the Archer installation to determine if object-level access controls are properly enforced on REST API requests.
    Affected if Object-level authorization validation is missing or inadequate for the REST API endpoint, allowing users to access objects outside their permitted scope.
  4. Examine API access audit logs
    Review RSA Archer audit logs for REST API GET requests where users accessed records or objects outside their expected permissions or data group assignments.
    Affected if Audit logs show evidence of users successfully accessing data objects they should not have been authorized to view through API requests.

A user is affected if RSA Archer version 6.1.0.0 through 6.9.2.x is installed with the REST API enabled and without proper object-level authorization controls on API endpoints.

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.0.1 or later
Fixed in 6.9.3.0.1
Interim mitigation

Implement proper authorization checks on the REST API endpoint to verify the authenticated user has permission to access the requested object before returning data. Consider adding consistent object-level access control validation across all API endpoints.

Recommended fix High confidence

6.9.3.0.1 or later

  1. Identify current RSA Archer version in the environment
  2. Review RSA Archer upgrade documentation and release notes for version 6.9.3.0.1
  3. Create a complete backup of the current Archer instance including database and configuration
  4. Test the upgrade in a non-production environment first
  5. Schedule maintenance window for production upgrade
  6. Execute upgrade to version 6.9.3.0.1 or later following official RSA Archer upgrade procedures
  7. Verify the IDOR vulnerability is remediated by testing the REST API endpoint access controls
  8. Validate that all existing functionality works correctly after upgrade
Caveat Review release notes for potential breaking changes between current version and 6.9.3.0.1; some custom integrations or configurations may require updates

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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