CVE-2023-37224
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 · uneditedAn issue in Archer Platform before v.6.13 fixed in v.6.12.0.6 and v.6.13.0 allows an authenticated attacker to obtain sensitive information via the log files.
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 confidenceThis is an information disclosure vulnerability in RSA Archer Platform where an authenticated attacker can access sensitive information through log files. The vulnerability exists in versions prior to v.6.12.0.6 and v.6.13.0, allowing privilege escalation via exposure of potentially confidential data in application logs.
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< 6.13.0.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Archer Platform installation locationLocate the Archer installation directory, typically found under the web application root (e.g., IIS web root or C:\Program Files\RSA Archer\). Check for the presence of the 'Archer' application folder and the 'bin' subdirectory containing Archer-related executables and DLLs.Affected if The Archer Platform application is installed and running.
-
Determine installed Archer Platform versionOpen the Windows Control Panel, go to Programs and Features, and locate 'RSA Archer' in the installed programs list to view the version. Alternatively, check the 'About' page within the Archer web application interface if accessible.Affected if The installed version is shown as anything less than 6.13.0.1 (or less than 6.12.0.6 if using the 6.12.x branch).
-
Locate application log filesNavigate to the Archer installation directory and locate the 'logs' or 'App_Data\logs' subdirectory. Common paths include C:\Program Files\RSA Archer\Archer\App_Data\logs\ or within the IIS website root under Archer\App_Data\logs\. List all .log files present.Affected if Log files exist in the expected Archer log directory.
-
Verify log file accessibilityRight-click on the log directory and select Properties, then check the Security tab to verify which user accounts have Read or Write permissions to the log files. Compare this against expected application service accounts and authorized administrators.Affected if Unauthorized or low-privilege authenticated users have Read access to log files containing sensitive data.
-
Examine log files for sensitive contentOpen recent log files using a text editor and search for patterns indicating sensitive data exposure: look for password parameters, session tokens, user credentials, PII fields, or SQL query content that may have been logged inadvertently.Affected if Log files contain plaintext passwords, credentials, session tokens, or other confidential data that should not be exposed.
You are affected if the installed RSA Archer Platform version is below 6.13.0.1 and log files containing sensitive data are accessible to authenticated users who should not have access to that information.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.13.0.1
Upgrade Archer Platform to version 6.12.0.6 or 6.13.0 or later to patch the vulnerability.
6.13.0.1 or later (alternatively 6.12.0.6)
- Upgrade Archer Platform to version 6.12.0.6 or 6.13.0.1 (or later) to remediate the sensitive information in logs vulnerability
- After upgrade, verify that log files no longer contain sensitive information by reviewing log configurations and conducting a security assessment
- Ensure proper access controls are in place to restrict access to log files to only authorized administrators
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37224 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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