dbcve.org
ArcherApplication · Rsa

CVE-2021-41594

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to 6.9.3.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
In RSA Archer 6.9.SP1 P3, if some application functions are precluded by the Administrator, this can be bypassed by intercepting the API request at the /api/V2/internal/TaskPermissions/CheckTaskAccess endpoint. If the parameters of this request are replaced with empty fields, the attacker achieves access to the precluded functions.

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

RSA Archer 6.9.SP1 P3 contains a broken access control vulnerability where the /api/V2/internal/TaskPermissions/CheckTaskAccess endpoint fails to properly enforce Administrator-imposed restrictions. By intercepting the API request and replacing parameters with empty fields, attackers can bypass the intended access controls and gain access to functions that should be precluded.

MitigationImplement server-side validation at the CheckTaskAccess endpoint to ensure task permissions are properly enforced regardless of request parameter values; consider adding CSRF tokens and re-validating permissions on each request.

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.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. Identify installed RSA Archer version
    Access the RSA Archer About page via the web interface (typically at /About.aspx) or check the installation manifest/config files on the server. Compare the version number against the affected range: >= 6.1.0.0 and < 6.9.3.3
    Affected if The installed version falls within 6.1.0.0 through 6.9.3.2
  2. Verify the CheckTaskAccess API endpoint is exposed
    Attempt to access the endpoint /api/V2/internal/TaskPermissions/CheckTaskAccess via HTTP request (e.g., using curl or browser developer tools). A successful HTTP 200 or 403 response (rather than 404) indicates the endpoint exists and is reachable
    Affected if The endpoint responds with any status code other than 404 (not found)
  3. Confirm task-based access control enforcement
    Using a low-privileged or non-administrator user account, send a request to the CheckTaskAccess endpoint and observe whether the application enforces role-based restrictions when request parameters are modified or left empty
    Affected if The application allows access to restricted functions or returns permission data when parameters are manipulated, indicating the access control bypass is present

You are affected if your RSA Archer version is between 6.1.0.0 and 6.9.3.2 inclusive and the CheckTaskAccess endpoint is accessible and permits parameter manipulation to bypass intended access restrictions.

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.3 or later
Fixed in 6.9.3.3
Interim mitigation

Implement server-side validation at the CheckTaskAccess endpoint to ensure task permissions are properly enforced regardless of request parameter values; consider adding CSRF tokens and re-validating permissions on each request.

Recommended fix High confidence

6.9.3.3 or later

  1. Schedule a maintenance window for the upgrade process
  2. Create a full backup of the RSA Archer database and configuration
  3. Test the upgrade in a non-production environment first
  4. Upgrade RSA Archer from the current version to version 6.9.3.3 or later
  5. Verify the upgrade was successful by logging into the Archer web interface
  6. Confirm the /api/V2/internal/TaskPermissions/CheckTaskAccess endpoint now properly enforces task permission restrictions
  7. Test that administrator-precluded functions remain inaccessible even when API request parameters are modified
Caveat Standard Archer upgrade precautions apply: backup database and configurations, test in staging environment before production deployment, and review release notes for any version-specific considerations

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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