dbcve.org
SiemApplication · Logpoint

CVE-2024-56085

MEDIUM · 5.9 CVSS v3.1 Published 2024-12-16
Fix available
A fix is available. Upgrade to 7.5.0 or later.
See remediation →
61/100
Remediation priority · Elevated
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. Authenticated users can inject payloads while creating Search Template Dashboard. These are executed, leading to Server-Side Template Injection.

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

Authenticated Logpoint users can inject malicious template payloads while creating Search Template Dashboards. These payloads are rendered by the server's template engine without proper sanitization, leading to Server-Side Template Injection (SSTI) that allows arbitrary code execution in the context of the application.

MitigationUpgrade to Logpoint version 7.5.0 or later. Until then, restrict dashboard creation permissions to trusted administrators only and monitor for suspicious dashboard 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:A/AC:H/PR:L/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 the installed Logpoint Siem version
    Access the Logpoint admin interface, typically via Settings > About or use command line tools provided by Logpoint to retrieve the current version number
    Affected if The installed version is below 7.5.0 (e.g., 7.4.0, 7.3.x, etc.)
  2. Determine which users can create dashboards
    Review user roles and permission settings in Logpoint's administration panel to identify which roles have dashboard creation privileges
    Affected if Non-administrator users or untrusted accounts have permission to create Search Template Dashboards
  3. Audit existing Search Template Dashboards
    Export or review the configuration of existing Search Template Dashboards in the Logpoint interface, looking for template syntax patterns commonly used in SSTI exploits (e.g., {{, {{=, ${
    Affected if Any dashboard contains template injection payloads or suspicious code patterns that were not intentionally created by administrators

Your environment is affected if you run Logpoint Siem version below 7.5.0 AND non-admin users can create Search Template Dashboards, or if existing dashboards contain malicious template injection code.

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 to Logpoint version 7.5.0 or later. Until then, restrict dashboard creation permissions to trusted administrators only and monitor for suspicious dashboard activity.

Recommended fix High confidence

Logpoint SIEM version 7.5.0

  1. 1. Check the current Logpoint SIEM version by accessing the administration console or running: `lpctl --version`
  2. 2. Create a full backup of the Logpoint configuration and data before upgrading
  3. 3. Download Logpoint version 7.5.0 or later from the official Logpoint portal or repository
  4. 4. Upgrade the Logpoint SIEM installation using the standard upgrade procedure (typically: `lpctl upgrade --file <path-to-upgrade-package>`)
  5. 5. After upgrade completes, verify the version is 7.5.0 or higher: `lpctl --version`
  6. 6. Test that authenticated users can no longer inject payloads in Search Template Dashboard functionality
  7. 7. Review system logs to confirm no post-upgrade issues
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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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