CVE-2023-24477
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 · uneditedIn certain conditions, depending on timing and the usage of the Chrome web browser, Guardian/CMC versions before 22.6.2 do not always completely invalidate the user session upon logout. Thus an authenticated local attacker may gain acces to the original user's session.
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 confidenceGuardian/CMC versions before 22.6.2 fail to fully invalidate user sessions upon logout under specific timing conditions when using Chrome browser. This session management flaw allows an authenticated local attacker to potentially hijack the original user's session after logout.
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< 22.6.2< 22.6.2CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 Guardian or CMC installation versionLocate the version information for your Nozomi Networks Guardian or CMC installation through the product interface, CLI, or system information filesAffected if The installed version is lower than 22.6.2 (for example, 22.5.0, 21.x, or earlier releases)
-
Determine the web browser used for accessIdentify whether users access the Guardian or CMC web interface using Google Chrome browserAffected if Chrome browser is used to access the web interface and the installed version is below 22.6.2
-
Verify session invalidation behavior on logoutLog in to the Guardian/CMC interface using Chrome, perform a logout, then attempt to use the browser back button or re-enter the URL to access authenticated resourcesAffected if After logout, previously authenticated pages or session-dependent content remains accessible without re-authentication
A user is affected if their Guardian or CMC installation version is below 22.6.2 and they access the web interface using Chrome browser, where sessions may not be fully invalidated upon logout.
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 · scoped22.6.2
Upgrade to Guardian/CMC version 22.6.2 or later which properly invalidates sessions on logout. Until patched, monitor for unauthorized session access and consider implementing additional session controls.
22.6.2 for both CMC and Guardian
- Upgrade CMC to version 22.6.2 or later
- Upgrade Guardian to version 22.6.2 or later
- After upgrade, verify that user sessions are properly invalidated upon logout
- Test with Chrome browser to confirm the session fixation issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-24477 — 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-24477 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