dbcve.org
SiemApplication · Logpoint

CVE-2024-48954

MEDIUM · 6.4 CVSS v3.1 Published 2024-11-07
Fix available
A fix is available. Upgrade to 7.5.0 or later.
See remediation →
69/100
Remediation priority · Elevated
No privileges 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.5.0. Unvalidated input during the EventHub Collector setup by an authenticated user leads to Remote Code 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 · moderate confidence

Unvalidated user input in the EventHub Collector setup functionality in Logpoint versions before 7.5.0 allows authenticated users to inject and execute arbitrary code on the underlying system, leading to full remote code execution.

MitigationUpgrade Logpoint to version 7.5.0 or later to obtain the patch for this vulnerability. Until upgrade is possible, restrict access to the EventHub Collector configuration to only highly trusted administrators and monitor for suspicious activity.

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

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

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 Logpoint installation version
    Access the Logpoint administrative interface or use the command-line interface to retrieve the current installed version. This is typically found in the system information, about page, or by running the appropriate version command for your Logpoint installation.
    Affected if The installed version is any version earlier than 7.5.0 (e.g., 7.4.x, 7.3.x, etc.)
  2. Locate EventHub Collector configuration
    Navigate to the Logpoint administrative console and locate the EventHub Collector settings or configuration panel. This is typically found under Data Sources, Collectors, or Integration settings depending on the interface layout.
    Affected if The EventHub Collector feature is present and accessible in the installation, regardless of whether it is actively configured.
  3. Verify if EventHub Collector is actively configured
    Examine the EventHub Collector configuration to determine if any EventHub endpoints or collectors are currently defined or actively receiving data.
    Affected if The EventHub Collector has any active collector configurations pointing to EventHub endpoints.
  4. Review EventHub Collector input parameters
    Inspect the EventHub Collector setup fields for any unexpected or suspicious values in connection strings, endpoint URLs, authentication parameters, or custom field inputs that may indicate injection attempts.
    Affected if Any EventHub Collector configuration contains unexpected characters, additional scripts, or parameters that were not intentionally entered by administrators.
  5. Check for unauthorized code execution artifacts
    Review system logs, audit logs, or execution logs for any unusual commands, scripts, or processes spawned from the EventHub Collector functionality or surrounding timeframes.
    Affected if There are log entries indicating arbitrary command execution or unexpected script invocations that correlate with EventHub Collector access.

You are affected if your Logpoint Siem version is before 7.5.0 AND the EventHub Collector feature is accessible or configured in your environment.

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.5.0 or later
Fixed in 7.5.0
Interim mitigation

Upgrade Logpoint to version 7.5.0 or later to obtain the patch for this vulnerability. Until upgrade is possible, restrict access to the EventHub Collector configuration to only highly trusted administrators and monitor for suspicious activity.

Recommended fix Moderate confidence

Logpoint SIEM 7.5.0

  1. Schedule a maintenance window for the Logpoint SIEM upgrade
  2. Ensure you have a complete backup of the Logpoint configuration and data
  3. Download Logpoint version 7.5.0 or later from the official Logpoint download portal
  4. Stop all Logpoint services before beginning the upgrade
  5. Run the Logpoint upgrade installer for version 7.5.0
  6. Follow the on-screen upgrade wizard instructions
  7. After upgrade completes, verify all Logpoint services are running
  8. Confirm the EventHub Collector functionality is working correctly
Caveat Review Logpoint 7.5.0 release notes for any configuration or feature changes that may affect existing setups

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

Fix this in Siem Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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