CVE-2024-34092
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 was discovered in Archer Platform 6 before 2024.04. Authentication was mishandled because lock did not terminate an existing session. 6.14 P3 (6.14.0.3) 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 · moderate confidenceRSA Archer Platform has a session management flaw where account lockout does not terminate existing active sessions, allowing authenticated access to persist after an account is locked.
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.14.0.3= 2024.03CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed RSA Archer Platform versionLocate the version information in the Archer administration interface under System Settings > General Settings, or check the installation/upgrade documentation for your instanceAffected if The installed version is 2024.03 or any version prior to 6.14.0.3
-
Confirm the exact version numberCompare your identified version against the affected ranges: versions < 6.14.0.3 or version = 2024.03 are vulnerableAffected if Your version falls within the affected ranges (less than 6.14.0.3 or equal to 2024.03)
-
Verify session termination behavior on account lockoutCreate a test account, establish an active session, then lock the account through the administration interface or by exceeding failed login attempts. Attempt to use the existing session token.Affected if The existing session remains valid and authenticated after the account is locked, indicating the vulnerability is present
-
Check session configuration settingsReview the session management or security configuration settings in Archer System Settings to determine if there is an option to terminate sessions on account lockout, and whether it is enabledAffected if Sessions persist after account lockout regardless of configuration settings, or no such termination option exists
You are affected if your RSA Archer Platform version is 2024.03 or any version lower than 6.14.0.3, and existing user sessions remain active after their accounts become locked.
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.14.0.3
Upgrade to Archer Platform version 2024.04 or 6.14 P3 (6.14.0.3) or later to ensure locked accounts properly terminate all active sessions.
6.14.0.3 (6.14 P3) or 2024.04
- Upgrade Archer Platform to version 6.14.0.3 (6.14 P3) or later
- Alternatively, upgrade to version 2024.04 or later
- After upgrade, verify that locking a user account now properly terminates all existing sessions
- Consult Archer release notes for any additional upgrade prerequisites or post-upgrade steps
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34092 — 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-2024-34092 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