CVE-2024-6097
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® Reporting versions prior to 2025 Q1 (19.0.25.211), information disclosure is possible by a local threat actor through an absolute path vulnerability.
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 Reporting versions prior to 2025 Q1 (19.0.25.211) contain an information disclosure vulnerability where a local attacker can obtain absolute file system paths through the application, potentially revealing sensitive directory structures that could aid in further exploitation.
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< 19.0.25.211CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Telerik Reporting installationLocate the Telerik Reporting assembly (Telerik.Reporting.dll) in the application bin directory or check the web.config/app.config for Telerik.Reporting version referencesAffected if Telerik Reporting is deployed in the environment
-
Determine the installed version numberRight-click Telerik.Reporting.dll, select Properties, then view the File Version attribute. Alternatively, check the assembly reference in the project file or NuGet package.config for the installed versionAffected if The version displayed is below 19.0.25.211
-
Verify the application is accessibleConfirm the Telerik Reporting service or web application is running and reachable via its endpointAffected if The reporting application is live and processing requests
-
Confirm path disclosure exposureTest the reporting endpoints with crafted requests known to trigger error responses that may expose absolute file paths in error messages or stack tracesAffected if Error responses contain absolute filesystem paths
The environment is affected if Telerik Reporting version is below 19.0.25.211 and the application is accessible, as the vulnerability allows disclosure of absolute paths through application error responses.
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 · scoped19.0.25.211
Upgrade Telerik Reporting to version 2025 Q1 (19.0.25.211) or later to address the absolute path disclosure vulnerability.
Telerik Reporting 19.0.25.211 (2025 Q1 release) or later
- 1. Backup the current Telerik Reporting installation and all associated databases
- 2. Download Telerik Reporting version 19.0.25.211 or later from the official Telerik website (docs.telerik.com)
- 3. Review the official upgrade guide at docs.telerik.com/reporting/upgrade
- 4. Test the upgrade in a non-production environment before deploying to production
- 5. Apply the upgrade following Telerik's standard installation procedures
- 6. Verify that the application functions correctly after the upgrade
- 7. Confirm the installed version matches or exceeds 19.0.25.211
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6097 — 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-6097 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