dbcve.org
Logstare CollectorApplication · Secuavail

CVE-2025-64695

HIGH · 7.8 CVSS v3.0 Published 2025-11-21
Fix available
A fix is available. Upgrade to 2.4.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Uncontrolled search path element issue exists in the installer of LogStare Collector (for Windows). If exploited, arbitrary code may be executed with the privilege of the user invoking the installer.

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

The LogStare Collector Windows installer suffers from an uncontrolled search path element vulnerability (DLL hijacking). The installer does not use fully qualified paths when loading libraries, allowing an attacker to place a malicious DLL in a directory that gets searched before the legitimate location. When a user runs the installer, any arbitrary code within the hijacked DLL executes with the same privileges as the user invoking the installer.

MitigationOnly download and run the LogStare Collector installer from verified, official sources. Ensure the download integrity is validated (e.g., checksums) and that the download directory is not writable by untrusted users. Consider running installers in isolated environments as a precautionary measure.

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
Logstare CollectorApplication
Affected:< 2.4.2

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 checks

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

  1. Locate LogStare Collector installation directory
    Search the filesystem for directories named 'LogstareCollector' or 'LogStare Collector', typically found under C:\Program Files\ or C:\Program Files (x86)\. Use the command: dir /s /b "C:\Program Files\*Logstare*" 2>nul
    Affected if The product directory exists on the system, indicating LogStare Collector is installed.
  2. Find the installer executable
    Search for installer files with patterns like 'LogStare*Collector*Setup*.exe' or 'Logstare*Collector*Installer*.exe' in the installation directory and common download locations. Check %TEMP% folder for recently downloaded installers.
    Affected if The installer executable exists on the system.
  3. Identify installed LogStare Collector version
    Check the version of installed files. Look for version information in file properties of the main executable (typically named LogstareCollector.exe or similar) in the installation directory. Right-click the executable, select Properties, and view the Details tab for the version number.
    Affected if The installed version number is less than 2.4.2, meaning the vulnerability is present.
  4. Check installer version if available
    If you have a copy of the installer, right-click the .exe file, select Properties, and examine the Details tab for Product Version or File Version. Compare this against the affected version range.
    Affected if The installer version is less than 2.4.2, indicating the DLL hijacking vulnerability exists in that installer.

You are affected if LogStare Collector version 2.4.2 or higher is not installed, as versions below 2.4.2 contain the DLL hijacking vulnerability in the Windows installer.

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 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Only download and run the LogStare Collector installer from verified, official sources. Ensure the download integrity is validated (e.g., checksums) and that the download directory is not writable by untrusted users. Consider running installers in isolated environments as a precautionary measure.

Recommended fix High confidence

LogStare Collector 2.4.2

  1. Obtain LogStare Collector installer version 2.4.2 or later from the official vendor website (www.logstare.com)
  2. Verify the installer file integrity (e.g., check digital signature, hash) before running
  3. Run the updated installer with the same privileges you normally would use
  4. Follow the installation prompts to complete the upgrade
  5. Verify the installation completed successfully

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

Fix this in Logstare Collector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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