dbcve.org
ArcherApplication · Archerirm

CVE-2023-48641

HIGH · 8.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 6.13.0.3 / 6.14.0.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Archer Platform 6.x before 6.14 P1 HF2 (6.14.0.1.2) contains an insecure direct object reference vulnerability. An authenticated malicious user in a multi-instance installation could potentially exploit this vulnerability by manipulating application resource references in user requests to bypass authorization checks, in order to gain execute access to AWF application resources.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in RSA Archer Platform versions 6.x before 6.14 P1 HF2. An authenticated attacker in a multi-instance environment can manipulate application resource references in requests to bypass authorization checks and gain unauthorized execute access to AWF (Archer Workflow) application resources.

MitigationUpgrade to Archer Platform 6.14 P1 HF2 (6.14.0.1.2) or later. Additionally, implement robust object-level authorization validation for all resource references and enforce proper instance isolation in multi-instance deployments.

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.1.2< 6.13.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check RSA Archer Platform version
    Navigate to the Archer Control Panel or About page in the Archer user interface to view the installed version. Alternatively, check the installation directory for version files or use the Archer System Administration > System Settings > About screen.
    Affected if The installed version is lower than 6.14.0.1.2 or is between 6.13.0.0 and 6.13.0.2 (i.e., < 6.13.0.3)
  2. Confirm multi-instance environment
    Check Archer System Administration > Instance Management or review the Archer configuration files for multiple instance definitions. Look for multiple instance configuration entries in the web.config or archer.config files.
    Affected if More than one instance is configured in the Archer deployment
  3. Verify AWF module is enabled
    Check if the Archer Workflow (AWF) application module is installed and enabled. Navigate to System Administration > Module Management or review the available applications in the Archer platform.
    Affected if AWF (Archer Workflow) application is installed and active in the environment
  4. Review instance isolation settings
    Examine the instance isolation configuration in the Archer web.config file or through System Administration > Instance Settings. Verify that cross-instance resource access controls are properly configured.
    Affected if Instance isolation is not properly enforced, allowing resource references to be manipulated across instances

The environment is affected if the installed Archer Platform version is below 6.14.0.1.2 (or below 6.13.0.3), a multi-instance environment exists, and the AWF module is enabled without proper instance isolation controls.

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.13.0.3 / 6.14.0.1.2 or later
Fixed in 6.13.0.36.14.0.1.2
Interim mitigation

Upgrade to Archer Platform 6.14 P1 HF2 (6.14.0.1.2) or later. Additionally, implement robust object-level authorization validation for all resource references and enforce proper instance isolation in multi-instance deployments.

Recommended fix High confidence

6.14 P1 HF2 (6.14.0.1.2) or later

  1. Schedule a maintenance window for the Archer platform upgrade
  2. Review the Archer 6.14 P1 HF2 (6.14.0.1.2) release notes and upgrade documentation for prerequisites
  3. Perform a full backup of the Archer database and configuration files
  4. Test the upgrade in a non-production environment first
  5. Apply the upgrade to production environment following the documented upgrade procedure
  6. Verify the installation by checking the version number in Archer Control Panel
  7. Test that AWF application resources are properly protected by authorization checks
Caveat Review Archer upgrade documentation for any configuration or integration changes required

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-2023-48641 — 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-2023-48641 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