dbcve.org
KendoreactFramework / library · Progress

CVE-2024-12629

HIGH · 7.2 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 9.4.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
In Progress® Telerik® KendoReact versions v3.5.0 through v9.4.0, 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 · moderate confidence

The vulnerability is a prototype pollution issue in Telerik KendoReact versions 3.5.0 through 9.4.0. Attackers can manipulate global prototype chain properties, potentially causing denial of service or enabling command injection through polluted prototype properties that are later used in unsafe operations.

MitigationUpgrade to a patched version of KendoReact beyond v9.4.0 as provided by Progress Telerik. If immediate patching is not feasible, implement strict input validation and object property whitelisting to prevent prototype pollution attacks.

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
KendoreactFramework / library
Affected:>= 3.5.0, < 9.4.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed KendoReact version
    Run 'npm list @progress/kendo-react-*' or inspect your package.json file to find the version of @progress/kendo-react packages
    Affected if The installed version is >= 3.5.0 and < 9.4.0
  2. Verify KendoReact version in node_modules
    Check the package.json file within node_modules/@progress/kendo-react-<component>/package.json for one of your installed KendoReact packages to confirm the exact version
    Affected if The confirmed version is 3.5.0 or higher but below 9.4.0
  3. Assess prototype pollution attack surface
    Review application code using KendoReact components that process external JSON input, user-controllable objects, or dynamic property assignment. Look for code paths where KendoReact parses or merges objects from untrusted sources without filtering __proto__, constructor, or prototype properties
    Affected if The application passes untrusted JSON or object data to KendoReact components without sanitizing these property keys

You are affected if KendoReact version is 3.5.0 through 9.3.x AND your application uses KendoReact to process untrusted input that could modify prototype properties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.4.0 or later
Fixed in 9.4.0
Interim mitigation

Upgrade to a patched version of KendoReact beyond v9.4.0 as provided by Progress Telerik. If immediate patching is not feasible, implement strict input validation and object property whitelisting to prevent prototype pollution attacks.

Recommended fix High confidence

Upgrade to KendoReact v9.4.0 or later

  1. 1. Identify all projects using @progress/kendo-react-* packages with versions between 3.5.0 and 9.3.0
  2. 2. Review project dependencies to confirm which specific KendoReact components are in use
  3. 3. Update package.json to specify version 9.4.0 or higher for all @progress/kendo-react packages
  4. 4. Run 'npm update' or 'npm install @progress/kendo-react-[component-name]@9.4.0' to apply the new versions
  5. 5. Test the application thoroughly to ensure all KendoReact components function correctly after the upgrade
  6. 6. Verify that the prototype pollution vulnerability is no longer present in the dependency tree
Caveat Review KendoReact v9.4.0 release notes for any breaking changes or API modifications that may affect your implementation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kendoreact Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12629 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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