dbcve.org
RemoteApplication · Teamviewer

CVE-2023-0837

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 15.42.8 or later.
See remediation →
57/100
Remediation priority · Elevated
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
An improper authorization check of local device settings in TeamViewer Remote between version 15.41 and 15.42.7 for Windows and macOS allows an unprivileged user to change basic local device settings even though the options were locked. This can result in unwanted changes to the configuration.

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

TeamViewer Remote client versions 15.41 through 15.42.7 for Windows and macOS contain an improper authorization check that fails to enforce locked local device settings. An unprivileged local user can bypass the intended locking mechanism and modify basic device configuration settings that should be restricted.

MitigationUpgrade TeamViewer Remote to version 15.42.7 or later. Review and verify that settings that should be locked are properly enforced after the update.

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
RemoteApplication
Affected:>= 15.41, < 15.42.8

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Check if TeamViewer Remote is installed
    On Windows, open Programs and Features or check C:\Program Files\TeamViewer. On macOS, check /Applications for TeamViewer.app or run 'ls /Applications | grep -i teamviewer'.
    Affected if TeamViewer Remote is not present on the system, the vulnerability does not apply.
  2. Determine installed TeamViewer Remote version
    On Windows, right-click TeamViewer in the Start menu and select 'App info', or open TeamViewer and go to Help > About TeamViewer. On macOS, right-click TeamViewer.app in Applications and select 'Get Info', or open TeamViewer and go to TeamViewer > About TeamViewer.
    Affected if The version number is within the affected range (15.41 through 15.42.7).
  3. Verify version against CVE range
    Compare your installed version number to the affected range: versions 15.41, 15.42, 15.42.1, 15.42.2, 15.42.3, 15.42.4, 15.42.5, 15.42.6, and 15.42.7 are all vulnerable. Versions below 15.41 or at 15.42.8 and later are not affected.
    Affected if Your installed version starts with 15.41 or 15.42.x where x is 0 through 7.
  4. Identify if locked device settings are in use
    Check TeamViewer management console for any deployed policies that lock device settings (such as password, security, or connection settings). On the local machine, attempt to access TeamViewer > Extras > Options and verify if any settings show a lock icon indicating they are controlled by policy.
    Affected if Locked settings policies are deployed and the local user could bypass that locking mechanism to modify restricted settings.

You are affected if TeamViewer Remote version 15.41 through 15.42.7 is installed AND you rely on TeamViewer's setting lock feature to restrict local device configuration changes.

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

Upgrade TeamViewer Remote to version 15.42.7 or later. Review and verify that settings that should be locked are properly enforced after the update.

Recommended fix High confidence

TeamViewer Remote version 15.42.8 or later

  1. Check the current TeamViewer Remote version by opening TeamViewer and going to Help > About TeamViewer (Windows) or TeamViewer > About TeamViewer (macOS)
  2. Navigate to www.teamviewer.com and download the latest version of TeamViewer Remote (version 15.42.8 or later)
  3. Install the downloaded version by running the installer and following the on-screen prompts
  4. Restart TeamViewer if prompted after installation
  5. Verify the fix by attempting to change locked device settings to confirm the authorization check is now properly enforced

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

Fix this in Remote Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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