dbcve.org
Telerik JustdecompileApplication · Progress

CVE-2024-0219

HIGH · 7.8 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to after 2019.1.118.0 or later.
See remediation →
80/100
Remediation priority · High
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 Telerik JustDecompile versions prior to 2024 R1, a privilege elevation vulnerability has been identified in the applications installer component.  In an environment where an existing Telerik JustDecompile install is present, a lower privileged user has the ability to manipulate the installation package to elevate their privileges on the underlying operating system.

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 confidence

Telerik JustDecompile versions prior to 2024 R1 contain a privilege elevation vulnerability in the installer component. In environments where JustDecompile is already installed, a lower-privileged user can manipulate the installation package to execute code with elevated (administrative/SYSTEM) privileges on the target system.

MitigationUpgrade to Telerik JustDecompile 2024 R1 or later. Until patched, restrict write access to installation directories and monitor for suspicious installer manipulation.

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
Telerik JustdecompileApplication
Affected:<= 2019.1.118.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify JustDecompile installation exists
    Check for the presence of Telerik JustDecompile on the system by looking for its installation directory (typically under Program Files or Program Files (x86)) or by querying the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'JustDecompile'
    Affected if JustDecompile is present on the system
  2. Retrieve installed version number
    Locate the JustDecompile installation and read the version from the executable properties (right-click JustDecompile.exe > Properties > Details), or query the Uninstall registry key for the DisplayVersion value
    Affected if Unable to determine version indicates potential incomplete detection
  3. Compare version against vulnerable range
    Compare the installed version number to the affected range: version 2019.1.118.0 or lower (any version prior to 2024 R1)
    Affected if Installed version is 2019.1.118.0 or lower - this means the installer component contains the privilege elevation flaw
  4. Check installation directory permissions (optional context)
    Review ACLs on the JustDecompile installation folder to determine if non-admin users have write access to installation directories - the vulnerability allows manipulation of the installer package
    Affected if Non-privileged users have write access to installation directories, which would allow exploitation of this vulnerability

The environment is affected if Telerik JustDecompile is installed with version 2019.1.118.0 or lower, as the installer component in these versions permits lower-privileged users to elevate to administrative or SYSTEM privileges.

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 a release after 2019.1.118.0
Interim mitigation

Upgrade to Telerik JustDecompile 2024 R1 or later. Until patched, restrict write access to installation directories and monitor for suspicious installer manipulation.

Recommended fix Moderate confidence

2024 R1 or later

  1. 1. Uninstall any existing Telerik JustDecompile installation from the affected machine
  2. 2. Download the latest version of Telerik JustDecompile from the official Telerik website (www.telerik.com)
  3. 3. Verify the downloaded installer file integrity using checksums if provided by Telerik
  4. 4. Run the installer with appropriate administrative privileges
  5. 5. Complete the installation process following the installer prompts
Caveat Upgrading from 2019.x to 2024 R1 may introduce UI changes, feature updates, or deprecations review release notes

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

Fix this in Telerik Justdecompile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0219 — 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-0219 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