dbcve.org
SeqApplication · Datalust

CVE-2024-29866

CRITICAL · 9.1 CVSS v3.1 Published 2024-03-21
Fix available
A fix is available. Upgrade to 2023.4.11151 / 2024.1.11146 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
Datalust Seq before 2023.4.11151 and 2024 before 2024.1.11146 has Incorrect Access Control because a Project Owner or Organization Owner can escalate to System privileges.

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

Datalust Seq contains an incorrect access control vulnerability allowing a Project Owner or Organization Owner to escalate privileges to System-level access. This privilege escalation occurs due to insufficient validation of user roles when performing certain actions within the application.

MitigationUpgrade Datalust Seq to version 2023.4.11151 or later (for the 2023.x branch) or version 2024.1.11146 or later (for the 2024.x branch). Verify that Owner-level accounts can no longer access System-level functions after upgrading.

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
SeqApplication
Affected:< 2023.4.11151>= 2024, < 2024.1.11146

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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. Determine installed Seq version
    Access the Seq web interface and navigate to the Settings or About page, or query the /api/about endpoint via the REST API to retrieve the running version number
    Affected if The displayed version falls outside the safe ranges: it is below 2023.4.11151 for the 2023.x branch, or it is 2024.0.x (between 2024.0.0 and 2024.1.11145 inclusive) for the 2024.x branch
  2. Verify System-level access exists
    Log in with a Project Owner or Organization Owner account and attempt to access System-level functions such as system settings, infrastructure monitoring, or administrative endpoints that should be restricted to System Administrators only
    Affected if The Owner-level account can successfully view or modify System-level settings or perform actions that require System Administrator privileges
  3. Check user role assignments
    Review the user profile or organization settings to confirm the account has only Project Owner or Organization Owner role without System Administrator role
    Affected if The tested account holds Project Owner or Organization Owner role but can still access System-level features
  4. Audit administrative access logs
    If Seq logging is enabled, review audit logs or event streams for instances where non-System Administrator accounts accessed system-level functions or APIs
    Affected if Logs show Owner-level accounts performing System Administrator actions

A user is affected if their Seq installation runs version 2023.4.11151 or earlier in the 2023.x branch, or version 2024.0.x through 2024.1.11145 in the 2024.x branch, AND Owner-level accounts can access System-level functions.

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 2023.4.11151 / 2024.1.11146 or later
Fixed in 2023.4.111512024.1.11146
Interim mitigation

Upgrade Datalust Seq to version 2023.4.11151 or later (for the 2023.x branch) or version 2024.1.11146 or later (for the 2024.x branch). Verify that Owner-level accounts can no longer access System-level functions after upgrading.

Recommended fix High confidence

Seq 2023.4.11151 or later for the 2023.x line; Seq 2024.1.11146 or later for the 2024.x line

  1. 1. Identify the current installed version of Seq by checking the Seq UI or running `seq version`
  2. 2. Stop the Seq service before upgrading
  3. 3. Upgrade to Seq version 2023.4.11151 or later (for 2023.x line) OR version 2024.1.11146 or later (for 2024.x line)
  4. 4. If using a package manager (Docker, NuGet, etc.), pull the specific fixed version tag
  5. 5. Restart the Seq service after upgrade
  6. 6. Verify the new version is running and the service is operational
  7. 7. Confirm the access control vulnerability is remediated by verifying that Project Owners and Organization Owners can no longer escalate to System privileges
Caveat No specific breaking changes documented in the CVE description; standard upgrade precautions apply (backup data before upgrading)

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

Fix this in Seq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29866 — 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-29866 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