CVE-2024-33865
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 linqi before 1.4.0.1 on Windows. There is an NTLM hash leak via the /api/Cdn/GetFile and /api/DocumentTemplate/{GUID] endpoints.
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 confidenceThe linqi library before version 1.4.0.1 on Windows contains an NTLM hash leak vulnerability via two API endpoints: /api/Cdn/GetFile and /api/DocumentTemplate/{GUID}. The NTLM authentication protocol can be coerced to reveal credential hashes, which can then be cracked or used in relay attacks to authenticate as the compromised user.
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< 1.4.0.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify Linqi installation and versionLocate the Linqi library files on the system and check the version information (typically found in assembly metadata, a version file, or the application manifest). Compare the installed version to the affected range of versions prior to 1.4.0.1.Affected if The installed version of Linqi is lower than 1.4.0.1
-
Confirm Windows environmentVerify that the Linqi instance is running on a Windows operating system, as this vulnerability is specific to the Windows implementation.Affected if The Linqi library is running on Windows
-
Check for exposed vulnerable API endpointsInspect web server logs or access logs for requests to the endpoints /api/Cdn/GetFile and /api/DocumentTemplate/{GUID}. If you have access to the application, attempt a request to these endpoints to confirm they respond.Affected if The endpoints /api/Cdn/GetFile and /api/DocumentTemplate/{GUID} are accessible and responding
-
Verify NTLM authentication is enabledReview the authentication configuration for the web server or application hosting Linqi. Check for NTLM authentication methods being enabled in IIS, Kestrel, or the application's configuration files.Affected if NTLM authentication is enabled and accepted by the Linqi application
A system is affected if it runs Linqi versions prior to 1.4.0.1 on Windows with the vulnerable endpoints exposed and NTLM authentication enabled.
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 · scoped1.4.0.1
Upgrade linqi to version 1.4.0.1 or later. Additionally, consider disabling NTLM authentication in favor of Kerberos and implementing SMB signing at the network level to prevent NTLM relay attacks.
1.4.0.1
- Upgrade linqi to version 1.4.0.1 or later
- Verify the upgrade was successful by checking the linqi version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33865 — 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-33865 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