dbcve.org
Telerik Test StudioApplication · Progress

CVE-2024-0833

HIGH · 7.8 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to 2023.3.1330 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 Test Studio versions prior to v2023.3.1330, a privilege elevation vulnerability has been identified in the applications installer component.  In an environment where an existing Telerik Test Studio 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

A local privilege escalation vulnerability exists in Telerik Test Studio's installer component for versions prior to v2023.3.1330. In environments with an existing installation, lower-privileged users can manipulate the installation package to gain elevated (OS-level) privileges.

MitigationUpgrade Telerik Test Studio to version v2023.3.1330 or later. Until patched, restrict physical and logical access to the installer and installation directories to prevent 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 Test StudioApplication
Affected:< 2023.3.1330

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 Telerik Test Studio installation exists
    Check for the product in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ for entries named 'Telerik Test Studio' or look in common install path C:\Program Files (x86)\Telerik\Test Studio
    Affected if No Telerik Test Studio installation found means this CVE does not apply to your environment
  2. Retrieve installed version number
    Open Windows Registry key for Telerik Test Studio (e.g., HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DisplayName}) and locate the DisplayVersion value, or right-click the Test Studio executable in its install directory and select Properties > Details to view the File Version
    Affected if Unable to determine version number prevents assessment - you must obtain the version to proceed
  3. Compare version against vulnerability threshold
    Compare your installed DisplayVersion to the fixed version 2023.3.1330. Version numbers follow format YYYY.MM.Build (e.g., 2023.3.1110 is before 2023.3.1330). Check both the major version components and the build number
    Affected if Your installed version is less than 2023.3.1330 (for example 2023.3.1110, 2023.2.908, or any earlier release) indicates your environment contains the vulnerable installer component

You are affected by CVE-2024-0833 if Telerik Test Studio is installed with any version number lower than 2023.3.1330.

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 2023.3.1330 or later
Fixed in 2023.3.1330
Interim mitigation

Upgrade Telerik Test Studio to version v2023.3.1330 or later. Until patched, restrict physical and logical access to the installer and installation directories to prevent manipulation.

Recommended fix Moderate confidence

Telerik Test Studio v2023.3.1330 or later

  1. 1. Backup any existing test projects and configurations
  2. 2. Download the latest Telerik Test Studio installer (version 2023.3.1330 or later) from the official Telerik website
  3. 3. Ensure you have administrative privileges on the system before initiating the upgrade
  4. 4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. 5. Verify the installation completed successfully by checking the version in the application
  6. 6. Re-run any existing test projects to confirm functionality is preserved

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

Fix this in Telerik Test Studio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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