dbcve.org
SiemApplication · Logpoint

CVE-2025-66361

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-28
Fix available
A fix is available. Upgrade to 7.7.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An issue was discovered in Logpoint before 7.7.0. Sensitive information is exposed in System Processes for an extended period during high CPU load.

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 confidence

Logpoint before version 7.7.0 exposes sensitive information in system process listings (such as process command-line arguments, environment variables, or memory contents) for an extended duration when the system experiences high CPU load conditions, allowing local or potentially remote attackers to obtain confidential data such as credentials or tokens visible in process information.

MitigationUpgrade Logpoint to version 7.7.0 or later; consider restricting access to system process monitoring tools and implementing network segmentation to limit exposure of process-level information.

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
SiemApplication
Affected:< 7.7.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Identify installed Logpoint version
    Locate the Logpoint installation and retrieve its version number, typically found in the product UI under 'About' or 'System Information', or via command-line tools provided by Logpoint
    Affected if The installed version is lower than 7.7.0 (e.g., 7.6.0, 7.5.x, etc.)
  2. Determine if process monitoring interfaces are accessible
    Check whether local or remote users can access system process listing tools or APIs on the Logpoint server (such as ps, top, process explorers, or Logpoint's built-in monitoring views)
    Affected if Process monitoring interfaces are exposed to untrusted users or networks without proper access controls
  3. Assess network exposure of process information
    Review network segmentation and access controls around the Logpoint system to determine if remote attackers could reach process monitoring endpoints or logs
    Affected if The Logpoint system or its process data is accessible over the network to untrusted parties or lacks proper network segmentation
  4. Check for credential exposure in process data
    During normal or high-load operation, examine whether process listings (command lines, environment variables) contain sensitive data such as passwords, API tokens, or secrets that should not be visible
    Affected if Process listings reveal credentials, tokens, or other sensitive information in command-line arguments or environment variables
  5. Verify CPU load handling behavior
    Under high CPU load conditions (simulate or observe), verify whether process information persists longer than expected in logs, memory dumps, or monitoring outputs
    Affected if Process information containing sensitive data remains accessible for extended periods during high CPU load conditions

You are affected if your Logpoint version is below 7.7.0 AND process monitoring data is accessible to local or remote attackers who could capture sensitive credentials or tokens visible in process listings.

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.

dbcve · scoped
Upgrade available Upgrade to 7.7.0 or later
Fixed in 7.7.0
Interim mitigation

Upgrade Logpoint to version 7.7.0 or later; consider restricting access to system process monitoring tools and implementing network segmentation to limit exposure of process-level information.

Recommended fix Moderate confidence

7.7.0

  1. 1. Back up the current Logpoint SIEM configuration and data before initiating any upgrade.
  2. 2. Review Logpoint upgrade documentation at servicedesk.logpoint.com for your current version's upgrade path to 7.7.0.
  3. 3. Schedule a maintenance window as upgrades may require system downtime.
  4. 4. Follow the documented upgrade procedure to upgrade the Logpoint SIEM to version 7.7.0.
  5. 5. After upgrade, verify the System Processes no longer expose sensitive information during high CPU load conditions.
  6. 6. Validate that all SIEM functionality and integrations operate correctly post-upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Siem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66361 — 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-2025-66361 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