CVE-2020-25095
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 · uneditedLogRhythm Platform Manager (PM) 7.4.9 allows CSRF. The Web interface is vulnerable to Cross-site WebSocket Hijacking (CSWH). If a logged-in PM user visits a malicious site in the same browser session, that site can perform a CSRF attack to create a WebSocket from the victim client to the vulnerable PM server. Once the socket is created, the malicious site can interact with the vulnerable web server in the context of the logged-in user. This can include WebSocket payloads that result in command execution.
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 confidenceLogRhythm PM 7.4.9 lacks proper Origin header validation and CSRF protection on WebSocket handshake requests. An authenticated user visiting a malicious site can have their browser forced to establish a WebSocket connection to the PM server, allowing the attacker to execute commands through WebSocket payloads in the context of the victim's session.
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= 7.4.9CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 LogRhythm Platform Manager installationLocate the LogRhythm Platform Manager installation and confirm the product name in your environmentAffected if The product is not LogRhythm Platform Manager (this CVE does not apply)
-
Determine the installed PM versionUse the system's version check mechanism (such as 'Help > About', a version command, or the PM diagnostics interface) to identify the exact version number of the Platform ManagerAffected if The installed version is exactly 7.4.9 - this specific version lacks Origin header validation and CSRF protection on WebSocket handshakes
-
Verify WebSocket endpoint accessibilityAttempt to access the WebSocket handshake endpoint on the PM server (typically ws:// or wss:// on the PM web interface port) to confirm the service is exposedAffected if The WebSocket endpoint is reachable from user browsers - this is required for the cross-site hijacking to be exploitable
-
Confirm authenticated session usageReview whether users access the PM web interface with authenticated sessions via a browserAffected if Users maintain active authenticated sessions in browsers when accessing PM - the attack requires a victim's authenticated browser to initiate the hijacked WebSocket connection
You are affected if LogRhythm Platform Manager is installed at exactly version 7.4.9, has an accessible WebSocket endpoint, and users access it with authenticated browser sessions.
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.
From vendor dataImplement strict Origin header validation on WebSocket handshake endpoints and embed anti-CSRF tokens into WebSocket connection initialization to prevent cross-site hijacking.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25095 — 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-2020-25095 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