CVE-2024-11629
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), using .NET Standard 2.0, the contents of a file at an arbitrary path can be exported to RTF.
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 confidenceThis is a path traversal vulnerability in Telerik Document Processing Libraries for .NET Standard 2.0 that allows attackers to read files from arbitrary filesystem paths and export their contents as RTF documents. The vulnerability requires no authentication mentioned, suggesting it may be exploitable remotely by providing a crafted file path to the RTF export functionality.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate Telerik Document Processing Libraries DLLsSearch for files named Telerik.Documents.Processing.dll, Telerik.Windows.Documents.Core.dll, or similar Telerik Document Processing DLLs in application bin directories, NuGet package folders, or installed program directories.Affected if The DLLs are present and their version is below 2025.1.205
-
Check the installed library versionRight-click the Telerik DLL, select Properties, then view the Details tab for Product Version, or use a .NET disassembler like ILSpy or dotPeek to inspect the assembly version attribute.Affected if The version shown is earlier than 2025.1.205 (for example, 2024.x.x, 2023.x.x, or earlier)
-
Identify applications using RTF export functionalitySearch source code for calls to RTF export methods such as RtfFormatProvider, ExportToRtf, or classes in the Telerik.Documents.FormatProviders.Rtf namespace.Affected if The application code calls RTF export methods from Telerik Document Processing Libraries
-
Verify the vulnerable attack surface is exposedReview application endpoints or input parameters that accept file paths and trigger RTF document generation. Check if user-supplied paths are passed directly to the Telerik export functionality.Affected if User-controlled file paths can reach the RTF export function without path validation
You are affected if Telerik Document Processing Libraries version below 2025.1.205 is present AND your application uses RTF export functionality with accessible file path inputs.
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 to Telerik Document Processing Libraries version 2025.1.205 or later. Audit all applications using this library to identify and remediate vulnerable instances.
Telerik Document Processing Libraries 2025.1.205 or later
- Identify all projects referencing Telerik Document Processing Libraries in your solution
- Update the Telerik.DocumentProcessing package reference to version 2025.1.205 or later
- Rebuild the solution to ensure the new package version is resolved
- Test document processing functionality to verify the upgrade does not break existing features
- Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11629 — 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-11629 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