CVE-2023-35857
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 Siren Investigate before 13.2.2, session keys remain active even after logging out.
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 confidenceSiren Investigate versions before 13.2.2 contain a session management flaw where session keys are not invalidated upon user logout. This allows session tokens to remain valid indefinitely, enabling attackers with access to these tokens to impersonate users even after they have logged out. The critical CVSS score reflects the ability to exploit this remotely without authentication, resulting in complete confidentiality and integrity compromise.
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< 13.2.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine installed Siren Investigate versionCheck the Siren Investigate version through the UI help/about page, or inspect the version file in the installation directory, or run: investigate --versionAffected if Version is below 13.2.2
-
Verify session token validity after logoutLog into Siren Investigate, capture your session token or cookie, then log out. Attempt to access an API endpoint or protected resource using the previously obtained tokenAffected if The session token still grants access after the user has logged out
-
Review session configuration settingsExamine the Siren Investigate configuration file (typically investigate.yml or investigate.conf) for session management settings such as sessionTimeout, tokenExpiration, or sessionStore configurationsAffected if No session invalidation mechanism is configured upon logout or session timeout is set to an excessively long duration
If the installed version is below 13.2.2 and session tokens remain valid after user logout, the environment is affected by this vulnerability.
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 · scoped13.2.2
Upgrade Siren Investigate to version 13.2.2 or later. As a temporary mitigation, consider implementing additional monitoring for suspicious session activity and enforcing session expiration policies at the infrastructure level (e.g., load balancer timeout).
13.2.2
- Upgrade Siren Investigate to version 13.2.2 or later to resolve the session key persistence issue.
- After upgrading, verify that session keys are properly invalidated upon logout.
- Consult the official Siren Investigate release notes at docs.support.siren.io for any additional configuration requirements.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35857 — 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-35857 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