dbcve.org
ArcherApplication · Archerirm

CVE-2023-32759

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-14
Fix available
A fix is available. Upgrade to 6.12.0.6 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
An issue in Archer Platform before v.6.13 and fixed in 6.12.0.6 and 6.13.0 allows an authenticated attacker to obtain sensitive information via a crafted URL.

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 Platform before v6.13 allows an authenticated attacker to obtain sensitive information via a crafted URL. The vulnerability is fixed in versions 6.12.0.6 and 6.13.0. This appears to be an information disclosure issue (likely IDOR or similar) requiring valid authentication.

MitigationApply the vendor-supplied patches (6.12.0.6 or 6.13.0) to the affected Archer Platform installation. Verify the patch resolves the vulnerability through functional testing.

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.12.0.6

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 Platform version
    Check the installed version of the RSA Archer Platform. This is typically visible in the Archer control panel, about page, or can be retrieved via the Archer web interface under Administration > System > About. Alternatively, check the installation directory for version manifest files or the root web.config for version information.
    Affected if The installed version is低于6.12.0.6或低于6.13.0（即任何早于6.12.0.6的版本）
  2. Confirm authentication is enabled
    Verify that the Archer Platform has authentication properly configured and enabled. This is typically found in Administration > Access Control > Authentication Methods or similar settings within the Archer web interface.
    Affected if Authentication is disabled or improperly configured, though the CVE states valid authentication is required for exploitation
  3. Verify patch installation status
    If updates have been applied, verify the exact patch level by checking Administration > System > Updates or Patch Information within the Archer interface. The fixed versions are 6.12.0.6 and 6.13.0.
    Affected if The system shows a version below 6.12.0.6 and no patches have been applied

You are affected if your RSA Archer Platform installation is at a version lower than 6.12.0.6 (and not 6.13.0 or higher) and accepts authenticated user sessions.

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.12.0.6 or later
Fixed in 6.12.0.6
Interim mitigation

Apply the vendor-supplied patches (6.12.0.6 or 6.13.0) to the affected Archer Platform installation. Verify the patch resolves the vulnerability through functional testing.

Recommended fix High confidence

6.12.0.6 or 6.13.0

  1. Schedule a planned maintenance window for the upgrade
  2. Perform a full backup of the current Archer installation and database
  3. Download Archer version 6.12.0.6 or 6.13.0 from the official Archer support portal
  4. Follow the standard Archer Platform upgrade procedure as documented in the installation guide
  5. Complete the upgrade and verify the build number reflects the fixed version
  6. Test that the vulnerability is mitigated by confirming sensitive information is no longer accessible via crafted URLs
  7. Verify normal platform functionality is working after the upgrade
Caveat Standard upgrade precautions apply; review release notes for any configuration or integration changes before proceeding

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