dbcve.org
Saml AuthenticationApplication · Logpoint

CVE-2024-36383

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-27
Fix available
A fix is available. Upgrade to 6.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Logpoint SAML Authentication before 6.0.3. An attacker can place a crafted filename in the state field of a SAML SSO-URL response, and the file corresponding to this filename will ultimately be deleted. This can lead to a SAML Authentication login outage.

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 confidence

Logpoint SAML Authentication before 6.0.3 lacks proper validation of the filename parameter in the state field of SAML SSO-URL responses. An attacker can craft a malicious filename that gets processed by the application's file deletion logic, causing arbitrary file deletion and resulting in SAML authentication login outages.

MitigationUpgrade to Logpoint SAML Authentication version 6.0.3 or later, which includes proper validation of the state field filename parameter.

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
Saml AuthenticationApplication
Affected:< 6.0.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Logpoint SAML Authentication version
    Locate the installed version of the Logpoint SAML Authentication component. This is typically found in the product's admin interface under 'About' or 'System Info', or via command line tools such as 'rpm -q' or 'dpkg -l' if the package name is known.
    Affected if The installed version is lower than 6.0.3
  2. Confirm SAML authentication is enabled
    Access the Logpoint administration panel and navigate to Authentication settings. Verify whether SAML authentication is configured and active for user logins.
    Affected if SAML authentication is enabled and being used as an authentication method
  3. Inspect SAML state parameter processing
    Review Logpoint application logs or capture SAML SSO-URL responses during authentication flows. Examine the 'state' parameter in SAML responses to see if the filename value is being processed by file deletion logic without validation.
    Affected if The application processes state field filename parameters without proper validation, allowing arbitrary file paths

The environment is affected if Logpoint SAML Authentication version is below 6.0.3 and SAML authentication is configured and actively used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.0.3 or later
Fixed in 6.0.3
Interim mitigation

Upgrade to Logpoint SAML Authentication version 6.0.3 or later, which includes proper validation of the state field filename parameter.

Recommended fix Moderate confidence

Logpoint SAML Authentication 6.0.3

  1. Verify current Logpoint SAML Authentication version by checking the installed package or Logpoint interface
  2. Download Logpoint SAML Authentication version 6.0.3 from the official Logpoint support portal (servicedesk.logpoint.com)
  3. Review release notes for version 6.0.3 to understand any migration requirements or prerequisites
  4. Backup current Logpoint configuration and database before performing the upgrade
  5. Install version 6.0.3 following the official upgrade documentation
  6. Verify the SAML Authentication functionality is working correctly after upgrade
  7. Confirm the vulnerability is remediated by testing the SAML SSO login flow
Caveat Review Logpoint 6.0.3 release notes for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Saml Authentication Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36383 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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