CVE-2024-33857
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.4.0. Due to a lack of input validation on URLs in threat intelligence, an attacker with low-level access to the system can trigger Server Side Request Forgery.
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 confidenceA Server-Side Request Forgery vulnerability exists in Logpoint versions before 7.4.0 due to insufficient input validation on URLs within the threat intelligence feature. An attacker with low-level system access can abuse this to make the server perform arbitrary HTTP requests to internal or external resources.
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.4.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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 installed Logpoint versionAccess the Logpoint administration interface or use the command 'lpctl --version' or check the About section in the Logpoint dashboard to determine the exact version numberAffected if The version displayed is below 7.4.0 (e.g., 7.3.0, 7.2.x, etc.)
-
Verify threat intelligence module is enabledNavigate to System Settings > Integrations or the Threat Intelligence section in the Logpoint admin panel to check if the threat intelligence feature is active and configuredAffected if The threat intelligence module is enabled and connected to any threat feed source
-
Review threat intelligence URL configurationInspect the threat intelligence integration settings to view the configured URLs or endpoints that Logpoint uses for threat data fetchingAffected if Custom or internal URLs are configured in the threat intelligence settings without proper validation restrictions
-
Check for recent suspicious outbound requestsReview Logpoint server logs (typically in /var/log/logpoint/ or via the Logpoint UI logs) for unusual HTTP requests originating from the Logpoint server to internal IP ranges or unfamiliar external domainsAffected if There are log entries showing HTTP requests from the Logpoint server to internal infrastructure (e.g., 10.x.x.x, 192.168.x.x, 127.x.x.x) or unexpected external URLs that were not intentionally configured
You are affected if your Logpoint installation is version 7.4.0 or earlier AND the threat intelligence feature is enabled and configured.
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.4.0
Upgrade to Logpoint 7.4.0 or later, which implements proper URL validation in the threat intelligence module to prevent SSRF attacks.
7.4.0
- Verify current Logpoint SIEM version by checking the system administration panel or using the command line interface
- Review current configuration and backup procedures for the existing installation
- Download Logpoint SIEM version 7.4.0 or later from the official Logpoint customer portal
- Follow Logpoint's standard upgrade procedure: stop the Logpoint services, run the upgrade installer, verify the upgrade completed successfully
- After upgrade, confirm the system is operational and review logs for any errors
- Verify that the threat intelligence URL input now properly validates and sanitizes URLs to prevent SSRF
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33857 — 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-33857 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