dbcve.org
LinqiApplication

CVE-2024-33863

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 /api/Cdn/GetFile local file inclusion.

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 confidence

A local file inclusion (LFI) vulnerability exists in linqi versions before 1.4.0.1 on Windows. The /api/Cdn/GetFile endpoint improperly validates user-supplied input, allowing attackers to use path traversal sequences (e.g., ../../) to access arbitrary files on the host system. This can lead to exposure of sensitive configuration files, credentials, or other confidential data.

MitigationUpgrade to linqi version 1.4.0.1 or later. Alternatively, implement strict input validation and path sanitization on the /api/Cdn/GetFile endpoint to restrict file access to intended directories only.

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 installation and version
    Locate the Linqi application installation directory and check the version information file or executable properties. Look for version metadata in the main application binary or a version file in the installation folder.
    Affected if The installed Linqi version is below 1.4.0.1 on a Windows system.
  2. Confirm Windows platform
    Verify that the Linqi instance is running on a Windows operating system by checking system information or the hosting environment.
    Affected if Linqi is running on Windows.
  3. Check endpoint accessibility
    Attempt to access the /api/Cdn/GetFile endpoint on the Linqi server using a web browser or HTTP client. This endpoint handles CDN file retrieval.
    Affected if The /api/Cdn/GetFile endpoint is exposed and reachable.
  4. Test for path traversal vulnerability
    Send an HTTP request to /api/Cdn/GetFile with path traversal sequences such as ../../../../windows/win.ini or similar relative path attempts to access system files outside the intended directory.
    Affected if The application returns content from files outside the intended directory, confirming the LFI vulnerability is exploitable.

A defender is affected if Linqi version is below 1.4.0.1, running on Windows, and the /api/Cdn/GetFile endpoint permits path traversal to read arbitrary files.

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 to linqi version 1.4.0.1 or later. Alternatively, implement strict input validation and path sanitization on the /api/Cdn/GetFile endpoint to restrict file access to intended directories only.

Recommended fix High confidence

Linqi 1.4.0.1

  1. 1. Back up the current Linqi installation and database before proceeding with any changes.
  2. 2. Download Linqi version 1.4.0.1 or later from the official source (linqi.help or www.linqi.de).
  3. 3. Replace the existing Linqi installation files with the new version 1.4.0.1 files.
  4. 4. Verify that the /api/Cdn/GetFile endpoint no longer allows arbitrary file access by testing with a non-sensitive local file path.
  5. 5. Review server logs for any signs of exploitation attempts targeting this vulnerability.
  6. 6. Ensure proper file permissions are set on the web server to prevent unauthorized access.
Caveat Review release notes for any configuration changes required when upgrading from older versions

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

Fix this in Linqi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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