CVE-2024-48951
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 · uneditedAn issue was discovered in Logpoint before 7.5.0. Server-Side Request Forgery (SSRF) on SOAR can be used to leak Logpoint's API Token leading to authentication bypass.
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 confidenceLogpoint before 7.5.0 contains a Server-Side Request Forgery (SSRF) vulnerability in its SOAR (Security Orchestration, Automation and Response) component. Attackers can exploit this SSRF to make the Logpoint server request internal resources, allowing leakage of the Logpoint API token. The stolen API token can then be used to bypass authentication and gain unauthorized access to the Logpoint platform.
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< 7.5.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Logpoint Siem installationLocate Logpoint installations in your environment and confirm the product name is Logpoint SiemAffected if Logpoint Siem is installed and version is below 7.5.0
-
Determine installed Logpoint versionCheck the Logpoint administration interface or run the command to retrieve the version number from the Logpoint systemAffected if The installed version is less than 7.5.0
-
Check if SOAR component is enabledExamine the Logpoint configuration to verify whether the SOAR (Security Orchestration, Automation and Response) module is activatedAffected if SOAR is enabled and the Logpoint version is below 7.5.0
-
Review HTTP access logs for internal requestsInspect Logpoint server logs for any suspicious HTTP requests to internal IP addresses or localhost that were initiated by the SOAR componentAffected if Logs show unexpected internal HTTP requests from the SOAR service
-
Audit for leaked API tokensSearch logs and network traffic for evidence of the Logpoint API token being transmitted to unexpected internal endpointsAffected if API tokens are found in logs or network flows pointing to internal resources
You are affected if Logpoint Siem version is below 7.5.0 and the SOAR component is enabled, as this combination allows the SSRF vulnerability to be exploited.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.5.0
Upgrade to Logpoint 7.5.0 or later to patch the SSRF vulnerability. Until patched, restrict network access to the SOAR interface and implement monitoring for suspicious internal HTTP requests.
Logpoint Siem 7.5.0 or later
- Obtain the Logpoint 7.5.0 or later version from the official Logpoint download repository or vendor
- Review the Logpoint upgrade documentation for your specific deployment type
- Perform a backup of the current configuration and data
- Execute the upgrade following the documented upgrade procedure
- Verify the SOAR component is functioning correctly after upgrade
- Confirm the SSRF vulnerability is remediated by verifying the API Token is no longer exposed through SSRF
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-48951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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