dbcve.org
ArcherApplication · Archerirm

CVE-2023-45357

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 6.13.0.2.2 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
Archer Platform 6.x before 6.13 P2 HF2 (6.13.0.2.2) contains a sensitive information disclosure vulnerability. An authenticated attacker could potentially obtain access to sensitive information via a popup warning message. 6.14 (6.14.0) is also a fixed release.

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

An authenticated attacker with valid credentials to RSA Archer Platform can obtain sensitive information through a popup warning message in versions before 6.13 P2 HF2 (6.13.0.2.2). The vulnerability allows disclosure of sensitive data that should not be exposed in the warning dialog.

MitigationUpgrade RSA Archer Platform to version 6.13 P2 HF2 (6.13.0.2.2) or 6.14.0 or later to remediate this vulnerability.

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.0, < 6.13.0.2.2

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 is present
    Identify if the target system is running RSA Archer Platform by checking your application inventory or observing the web interface for RSA Archer login pages
    Affected if RSA Archer Platform is installed in the environment
  2. Locate version information in the application
    Access the version through the Archer administration interface, typically found under Help > About, System Settings > General, or the login page footer. Check any version display pages in the web UI
    Affected if Version information cannot be located or retrieved
  3. Compare version against vulnerable range
    Take the identified version and determine if it falls within the affected range: version >= 6.0 AND version < 6.13.0.2.2
    Affected if Installed version is 6.0 or higher but below 6.13.0.2.2 (6.13 P2 HF2)
  4. Verify authentication mechanism is enabled
    Confirm that user authentication is enabled in the Archer system configuration, as the vulnerability requires valid credentials to exploit
    Affected if Authentication is enabled and version falls within the vulnerable range

The environment is affected if RSA Archer Platform is running version 6.0 or higher but below 6.13.0.2.2 and user authentication is enabled.

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.2.2 or later
Fixed in 6.13.0.2.2
Interim mitigation

Upgrade RSA Archer Platform to version 6.13 P2 HF2 (6.13.0.2.2) or 6.14.0 or later to remediate this vulnerability.

Recommended fix High confidence

6.13.0.2.2 (6.13 P2 HF2) or 6.14.0

  1. 1. Identify current Archer Platform version by navigating to Administration > System Settings > About Archer
  2. 2. Plan upgrade to one of the fixed releases: 6.13 P2 HF2 (6.13.0.2.2) or 6.14.0
  3. 3. Create a full backup of the Archer database and file system
  4. 4. Test the upgrade in a non-production/staging environment first
  5. 5. Schedule maintenance window for production upgrade
  6. 6. Execute upgrade to the chosen fixed version (6.13.0.2.2 or 6.14.0)
  7. 7. Verify the upgrade was successful and test critical functionality
  8. 8. Confirm the vulnerability is resolved by checking the About page shows the fixed version
Caveat Review Archer upgrade documentation for any configuration changes or prerequisites required for your current version to the target fixed version

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

Fix this in Archer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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