CVE-2024-29865
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 · uneditedLogpoint before 7.1.0 allows Self-XSS on the LDAP authentication page via the username to the LDAP login form.
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.1.0 contains a Self-XSS vulnerability in the LDAP authentication page where the username field does not properly sanitize input, allowing injection of malicious JavaScript that executes in the authenticated user's browser session.
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.1.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Determine installed Logpoint versionNavigate to the Logpoint admin interface and locate the version information, typically found under Settings > About or by running 'lpctl --version' via command lineAffected if The installed version is below 7.1.0
-
Check if LDAP authentication is enabledAccess Logpoint admin panel and go to Settings > Authentication > LDAP to verify whether LDAP authentication is configured and activeAffected if LDAP authentication is enabled and the version is below 7.1.0
-
Verify LDAP login page is accessibleConfirm the LDAP login endpoint is reachable (typically at the login page with LDAP authentication option) without requiring prior authenticationAffected if The LDAP login form is accessible and the version is below 7.1.0
The environment is affected if running Logpoint Siem version below 7.1.0 with LDAP authentication configured and the LDAP login page is accessible
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.1.0
Upgrade Logpoint to version 7.1.0 or later which contains the patch for the XSS vulnerability in the LDAP login form username field.
Logpoint SIEM 7.1.0
- Identify current Logpoint SIEM version by checking the system information or admin console
- Schedule a maintenance window for the upgrade process
- Download Logpoint SIEM version 7.1.0 or later from the official vendor portal (servicedesk.logpoint.com)
- Backup the current Logpoint configuration and database according to vendor backup procedures
- Follow Logpoint's official upgrade documentation to apply version 7.1.0
- Verify the upgrade was successful by checking the version number in the admin interface
- Confirm the LDAP authentication page no longer reflects user input without proper encoding
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29865 — 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-29865 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