dbcve.org
Platform ManagerApplication · Logrhythm

CVE-2020-25096

HIGH · 8.8 CVSS v3.1 Published 2020-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
LogRhythm Platform Manager (PM) 7.4.9 has Incorrect Access Control. Users within LogRhythm can be delegated different roles and privileges, intended to limit what data and services they can interact with. However, no access control is enforced for WebSocket-based communication to the PM application server, which will forward requests to any configured back-end server, regardless of whether the user's access rights should permit this. As a result, even the most low-privileged user can interact with any back-end component that has a LogRhythm agent installed.

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 confidence

LogRhythm PM 7.4.9 fails to enforce role-based access controls on WebSocket communications. The Platform Manager server accepts WebSocket requests and forwards them to backend components without validating whether the requesting user's privileges permit access to those specific resources, allowing privilege escalation.

MitigationImplement authorization checks on WebSocket message handlers to validate user permissions before forwarding requests to backend servers, and consider network segmentation to limit which backend components low-privileged users can reach.

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
Platform ManagerApplication
Affected:= 7.4.9

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LogRhythm Platform Manager is installed
    Locate the LogRhythm Platform Manager installation on the system - typically found in the LogRhythm installation directory, often under C:\Program Files\LogRhythm\Platform Manager or /opt/logrhythm/pm
    Affected if The product is not present on the system, the vulnerability does not apply
  2. Verify the installed version is 7.4.9
    Check the Platform Manager version information - this is typically accessible via the product's UI under About/Version, or via the installer/registry entries, or by querying the PM service
    Affected if The installed version is not exactly 7.4.9, the user is not affected by this specific CVE
  3. Determine if WebSocket communications are enabled
    Check the Platform Manager configuration for WebSocket endpoint settings - look for WebSocket listener configurations in the PM config files or examine if ws:// or wss:// endpoints are active
    Affected if WebSocket functionality is disabled or not configured, the specific attack vector is not available
  4. Check WebSocket authorization configuration
    Inspect the Platform Manager's WebSocket message handler configuration for role-based access control settings - examine whether the PM validates user permissions before forwarding WebSocket requests to backend components
    Affected if No RBAC validation is found on WebSocket handlers, the environment is vulnerable

A user is affected only if LogRhythm Platform Manager version 7.4.9 is installed with WebSocket communications enabled and without role-based access control validation on WebSocket message handlers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authorization checks on WebSocket message handlers to validate user permissions before forwarding requests to backend servers, and consider network segmentation to limit which backend components low-privileged users can reach.

Fix this in Platform Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25096 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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