CVE-2024-11343
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 · uneditedIn Progress® Telerik® Document Processing Libraries, versions prior to 2025 Q1 (2025.1.205), unzipping an archive can lead to arbitrary file system access.
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 confidenceTelerik Document Processing Libraries versions prior to 2025 Q1 (2025.1.205) contain a path traversal vulnerability during archive extraction. When unzipping archives, the library does not properly sanitize file paths containing '../' sequences, allowing attackers to craft malicious archives that write files to arbitrary locations outside the intended extraction directory.
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< 2025.1.205CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Telerik Document Processing Libraries versionCheck the assemblies or NuGet packages referenced in your project for Telerik.Documents.Core, Telerik.Documents.Zip, or similar Telerik Document Processing assembly versions. In .NET applications, examine the bin folder or project dependencies for version information.Affected if The installed version is lower than 2025.1.205
-
Determine if archive extraction is performedSearch your codebase for calls to ZipArchive extraction methods, Telerik ZipLibrary extraction functions, or any code that uses the library to unzip archives. Look for patterns like ExtractToDirectory, Extract, or similar extraction methods from Telerik document processing namespaces.Affected if Your application uses Telerik Document Processing Libraries to extract archives
-
Check if untrusted archives are processedReview whether the archive extraction handles files from external or untrusted sources such as user uploads, downloaded files, or data from network endpoints that could be controlled by attackers.Affected if The application extracts archives from sources outside the trusted application deployment context
You are affected if the installed Telerik Document Processing Libraries version is below 2025.1.205 AND your application uses the library to extract archives, particularly from user-provided or untrusted sources.
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 · scoped2025.1.205
Upgrade Telerik Document Processing Libraries to version 2025.1.205 or later. Validate that any archive extraction in applications using this library properly validates and sanitizes extracted file paths as an additional defense-in-depth measure.
2025.1.205
- Identify the current version of Telerik Document Processing Libraries in use within your application
- Download Telerik Document Processing Libraries version 2025.1.205 (Q1 2025) or later from the official Telerik website (docs.telerik.com)
- Replace the existing Telerik Document Processing Libraries DLLs in your application with the updated versions
- Rebuild and redeploy your application
- Test that archive unzipping functionality works correctly and that the path traversal vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11343 — 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-11343 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