CVE-2024-7295
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® Report Server versions prior to 2024 Q4 (10.3.24.1112), the encryption of local asset data used an older algorithm which may allow a sophisticated actor to decrypt this information.
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 confidenceProgress Telerik Report Server versions prior to 2024 Q4 (10.3.24.1112) use a weak, older encryption algorithm for local asset data. This allows a sophisticated attacker to potentially decrypt stored sensitive information, achieving unauthorized confidentiality access.
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< 10.3.24.1112CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Check installed Telerik Report Server versionAccess the Report Server administration interface or check the product documentation for the version. Typically found in the About or System Information section of the web management console, or by examining the installed application binaries and assemblies.Affected if The installed version is lower than 10.3.24.1112 (for example, 10.2.24.x, 10.1.x, earlier major versions).
-
Assess sensitivity of stored dataExamine the contents of the local asset storage to determine if sensitive information such as database connection strings, credentials, personal data, or confidential business data is present in stored reports or configurations.Affected if The local storage contains sensitive information (credentials, connection strings, personal data, proprietary report content) that would be valuable to an attacker.
A user is affected if their Telerik Report Server version is below 10.3.24.1112 AND they have local asset storage enabled containing sensitive data that could be decrypted using the weak encryption algorithm.
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 · scoped10.3.24.1112
Upgrade Telerik Report Server to version 10.3.24.1112 or later, which implements modern encryption. If immediate upgrade is not possible, identify and protect the storage locations containing locally-encrypted asset data.
10.3.24.1112 (2024 Q4 release)
- 1. Identify the current Telerik Report Server version by accessing the Reports configuration or administration interface
- 2. Create a complete backup of the Report Server database and configuration files
- 3. Download Telerik Report Server version 10.3.24.1112 (2024 Q4) or later from the official Telerik website
- 4. Stop the Telerik Report Server service before beginning the upgrade
- 5. Run the installer for the new version, following the upgrade prompts
- 6. Start the Report Server service after installation completes
- 7. Verify the upgrade was successful by checking the version number in the administration interface
- 8. Test that reports and functionality are working correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7295 — 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-7295 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