CVE-2024-33860
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. It allows Local File Inclusion (LFI) when an arbitrary File Path is used within the File System Collector. The content of the file specified can be viewed in the incoming logs.
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 confidenceLogpoint before version 7.4.0 contains a Local File Inclusion vulnerability in its File System Collector component. An attacker can specify an arbitrary file path through the collector configuration and read the contents of any accessible file on the system, with the file content being displayed in the incoming logs.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check installed Logpoint versionAccess the Logpoint administration interface or run the command: logpoint --version or check the About section in the web UI. Compare the version number to 7.4.0.Affected if Version is below 7.4.0
-
Verify File System Collector statusNavigate to the Collectors section in the Logpoint administration panel. Identify whether the File System Collector module is enabled and configured.Affected if File System Collector is enabled and running
-
Review File System Collector configurationInspect the File System Collector settings. Look for any collector jobs configured with file path parameters pointing to sensitive system files or unusual directories.Affected if Collector paths point to arbitrary locations outside expected log directories
-
Examine incoming logs for unexpected file contentsSearch the Logpoint log viewer for entries containing contents of system files (e.g., /etc/passwd, Windows system files) that were not intentionally configured as log sources.Affected if Logs contain unexpected file contents from system directories
-
Check collector access logsReview the File System Collector logs or audit trails for any file read operations targeting paths outside the intended monitoring scope.Affected if Collector has accessed files outside its defined monitoring directory
You are affected if running Logpoint version below 7.4.0 with the File System Collector 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 Logpoint to version 7.4.0 or later to patch the LFI vulnerability in the File System Collector. Until upgraded, restrict access to the File System Collector configuration to trusted personnel only.
7.4.0
- Identify the current Logpoint SIEM version by accessing the administration interface or running: logpoint --version
- Review the upgrade documentation at logpoint.com for version 7.4.0 to understand prerequisites and procedures
- Create a complete backup of the Logpoint configuration and database before upgrading
- Upgrade the Logpoint SIEM installation to version 7.4.0 or later following the official upgrade procedure
- After upgrade, verify the File System Collector configuration does not allow arbitrary file paths outside the intended collection directory
- Confirm the version upgrade was successful by checking: logpoint --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33860 — 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-33860 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