dbcve.org
LinqiApplication

CVE-2024-33868

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.4.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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 linqi before 1.4.0.1 on Windows. There is LDAP injection.

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

The linqi library before version 1.4.0.1 on Windows contains an LDAP injection vulnerability. User-supplied input used in LDAP queries is not properly sanitized, allowing attackers to manipulate LDAP statements to bypass authentication, extract unauthorized information from the directory service, or execute arbitrary LDAP commands.

MitigationUpgrade linqi to version 1.4.0.1 or later. If upgrading is not immediately possible, implement strict input validation and parameterized LDAP query construction to sanitize all user-supplied input before use in LDAP queries.

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
LinqiApplication
Affected:< 1.4.0.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify linqi library version
    Locate the linqi library DLL or NuGet package in your project. Check the file version property, or inspect the packages.config / .csproj file for the linqi package reference version number.
    Affected if The version is lower than 1.4.0.1
  2. Confirm LDAP query usage
    Search your codebase for usage of Linqi LDAP query methods (typically methods that execute LDAP searches or queries against Active Directory or other LDAP directories). Look for code that initializes Linqi LDAP connections.
    Affected if Your application uses Linqi to execute LDAP queries
  3. Identify user input in LDAP context
    Review the LDAP query code paths and trace whether any HTTP request parameters, form inputs, user credentials, or other user-supplied data flow into the LDAP query construction or filtering logic.
    Affected if User-supplied input is passed directly into LDAP query parameters without apparent sanitization or parameterized query construction
  4. Check for input validation
    Inspect the LDAP query construction code for presence of input validation, sanitization routines, or use of parameterized LDAP query builders that separate query structure from user data.
    Affected if No input validation or parameterized query construction is found between user input and LDAP query execution

You are affected if your linqi library version is below 1.4.0.1 AND your application passes unsanitized user input directly into LDAP queries.

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 1.4.0.1 or later
Fixed in 1.4.0.1
Interim mitigation

Upgrade linqi to version 1.4.0.1 or later. If upgrading is not immediately possible, implement strict input validation and parameterized LDAP query construction to sanitize all user-supplied input before use in LDAP queries.

Recommended fix High confidence

1.4.0.1 or later

  1. 1. Check current Linqi version by running 'linqi --version' or checking the installed software information
  2. 2. Download Linqi version 1.4.0.1 or later from the official source at linqi.help or www.linqi.de
  3. 3. Create a backup of current Linqi configuration files and data
  4. 4. Stop any running Linqi services or processes
  5. 5. Install the upgraded Linqi 1.4.0.1 version
  6. 6. Restore the configuration from the backup if needed
  7. 7. Start the Linqi service and verify successful startup
  8. 8. Confirm the installed version is 1.4.0.1 or later using 'linqi --version'

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

Fix this in Linqi Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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