dbcve.org
SoarApplication · Logpoint

CVE-2024-48952

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. SOAR uses a static JWT secret key to generate tokens that allow access to SOAR API endpoints without authentication. This static key vulnerability enables attackers to create custom JWT secret keys for unauthorized access to these endpoints.

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

Logpoint SOAR before version 7.5.0 uses a hardcoded static JWT secret key to sign authentication tokens. Attackers who discover this static secret can craft arbitrary JWT tokens to bypass authentication and access SOAR API endpoints without valid credentials.

MitigationUpgrade Logpoint to version 7.5.0 or later which implements dynamic JWT secret key generation. If immediate upgrade is not possible, restrict network access to SOAR API endpoints and monitor for anomalous API access patterns.

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
SoarApplication
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 SOAR installation version
    Use the product's built-in version checking mechanism (such as the /api/system/info endpoint, the web UI's about page, or the command line tool 'lpctl version') to retrieve the currently installed Logpoint SOAR version
    Affected if The installed version is lower than 7.5.0 (for example, 7.4.0, 7.3.0, etc.)
  2. Verify JWT authentication is enabled
    Confirm that the SOAR instance has API access and JWT-based authentication is active by attempting to access the authentication endpoints or reviewing the system configuration for API/JWT settings
    Affected if API endpoints are exposed and JWT authentication is in use (this is the default configuration)
  3. Check for unexpected JWT tokens in logs
    Review SOAR authentication and API access logs for any anomalous JWT tokens, particularly those with unusual claims or from unexpected sources, using the log search functionality or examining access logs
    Affected if Logs contain JWT tokens that were not issued by your own authentication system or show authentication anomalies

You are affected if your Logpoint SOAR installation is version 7.5.0 or earlier, and the API interface with JWT authentication is enabled and accessible.

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 which implements dynamic JWT secret key generation. If immediate upgrade is not possible, restrict network access to SOAR API endpoints and monitor for anomalous API access patterns.

Recommended fix High confidence

Logpoint SOAR 7.5.0 or later

  1. 1. Back up the current Logpoint SOAR configuration and database according to Logpoint backup procedures.
  2. 2. Download the Logpoint SOAR 7.5.0 (or latest stable) upgrade package from the official Logpoint portal at docs.logpoint.com or servicedesk.logpoint.com.
  3. 3. Stop all SOAR services and ensure no active connections or running playbooks during the upgrade process.
  4. 4. Apply the upgrade package using Logpoint's documented upgrade procedure (refer to the official installation/upgrade guide for version 7.5.0).
  5. 5. After upgrade completion, verify that the SOAR version displays as 7.5.0 or later in the system information or about page.
  6. 6. Test API endpoint access to confirm JWT authentication is functioning with the new (non-static) secret key mechanism.
  7. 7. If any custom integrations or scripts rely on JWT token generation, update them to use the new authentication method as documented in the 7.5.0 release notes.
Caveat Review 7.5.0 release notes for potential changes to API authentication behavior that may affect existing integrations or automated scripts

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

Fix this in Soar 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 the upgrade done

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-2024-48952 — 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-48952 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