CVE-2024-33858
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. A path injection vulnerability is seen while adding a CSV enrichment source. The source_name parameter could be changed to an absolute path; this will write the CSV file to that path inside the /tmp directory.
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 confidenceA path injection vulnerability in Logpoint before 7.4.0 allows authenticated users to manipulate the source_name parameter when adding a CSV enrichment source. By providing an absolute path, an attacker can write CSV files to arbitrary locations within the /tmp directory, potentially overwriting existing files or creating new files in unintended locations.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Logpoint versionAccess Logpoint admin interface or run 'logpoint --version' or check /var/log/logpoint/version file to determine the installed Siem versionAffected if Version is below 7.4.0
-
Verify CSV enrichment feature accessCheck if the authenticated user has permissions to add or modify CSV enrichment sources in the Logpoint admin console under Configuration > Enrichment SourcesAffected if User has administrative or enrichment configuration privileges and version is below 7.4.0
-
Inspect /tmp for unexpected CSV filesList files in /tmp directory using 'ls -la /tmp/' and look for CSV files that were not created by legitimate administrative processesAffected if Unexpected or unknown CSV files exist in /tmp directory indicating potential exploitation
You are affected if your Logpoint Siem version is below 7.4.0 and you have users with access to the CSV enrichment feature, especially administrative users.
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 version 7.4.0 or later which contains the patch for this vulnerability. As a compensating control, restrict administrative access to the CSV enrichment feature and monitor /tmp for unexpected file creation.
7.4.0
- 1. Verify current Logpoint SIEM version by checking the system information or contacting Logpoint support
- 2. If running a version lower than 7.4.0, plan for an upgrade to version 7.4.0 or later
- 3. Back up all current configurations and data according to Logpoint backup procedures
- 4. Schedule a maintenance window for the upgrade process
- 5. Follow Logpoint's official upgrade documentation to update to version 7.4.0 or latest stable release
- 6. After upgrade, verify the CSV enrichment source functionality works correctly with proper file paths
- 7. Confirm the vulnerability is remediated by testing that source_name parameter now rejects absolute paths
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-33858 — 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-33858 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