CVE-2024-11628
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® Kendo UI for Vue versions v2.4.0 through v6.0.1, an attacker can introduce or modify properties within the global prototype chain which can result in denial of service or command injection.
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 confidenceThis is a prototype pollution vulnerability in Telerik Kendo UI for Vue versions 2.4.0 through 6.0.1. The flaw allows attackers to inject or modify properties in the global JavaScript prototype chain, which can be leveraged to cause denial of service or achieve command injection in affected applications.
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>= 2.4.0, < 6.1.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Check installed Kendo UI for Vue versionInspect your package.json file or run 'npm list @progress/kendo-vue-grid' (or relevant Kendo package) to see the exact version installedAffected if version is 2.4.0 through 6.0.1 (inclusive)
-
Identify all Kendo Vue packages in useSearch your package.json for all @progress/kendo-vue-* packages and list their versionsAffected if any Kendo Vue package is at version 2.4.0 - 6.0.1 while others are below 6.1.0
-
Verify prototype pollution audit capabilitySearch your codebase for any custom property assignments to Object.prototype, __proto__, or constructor.prototype that may have been added as exploitation artifactsAffected if unexpected prototype modifications are found in client-side JavaScript
-
Check for suspicious runtime behaviorOpen browser developer console in your running application and inspect 'Object.prototype' properties for unexpected enumerable properties that were not defined by your applicationAffected if Object.prototype contains unexpected properties your application did not create
You are affected if any Kendo UI for Vue package in your application is version 2.4.0 or higher but below 6.1.0, or if prototype pollution artifacts are found in your client-side code.
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 · scoped6.1.0
Upgrade Kendo UI for Vue to a version beyond v6.0.1 (or apply vendor-supplied patches) and audit client-side code for any exploitation artifacts.
Upgrade to Kendo UI for Vue version 6.1.0 or later (e.g., ^6.1.0)
- Check the current version of @progress/kendo-vue-* packages in your package.json file
- Update the version of @progress/kendo-vue-* packages in package.json to ^6.1.0 or later (e.g., ^6.1.0, ^6.2.0)
- Run 'npm install' or 'yarn install' to download and install the updated packages
- Verify the installed version matches 6.1.0 or later using 'npm list @progress/kendo-vue-grid' or similar
- Test your application thoroughly to ensure the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11628 — 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-11628 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