dbcve.org
Thermoscan IpApplication · Proges

CVE-2024-31202

HIGH · 7.8 CVSS v3.1 Published 2024-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A “CWE-732: Incorrect Permission Assignment for Critical Resource” in the ThermoscanIP installation folder allows a local attacker to perform a Local Privilege Escalation.

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

ThermoscanIP installs with overly permissive file system ACLs on its installation folder, allowing any local user to modify executable files or configurations. A local attacker can exploit this misconfiguration to replace legitimate binaries with malicious ones that execute with elevated (administrator or SYSTEM) privileges.

MitigationRestrict permissions on the ThermoscanIP installation folder to follow least-privilege principles: remove write access for non-admin users, ensure only authorized service accounts have modify permissions, and verify executable files are not writable by low-privilege users.

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
Thermoscan IpApplication
Affected:= 20211103

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. Locate the ThermoscanIP installation directory
    Check common installation paths such as C:\Program Files\Proges\ThermoscanIP, C:\Program Files (x86)\Proges\ThermoscanIP, or search for folders containing 'ThermoscanIP' using dir /s /b C:\*ThermoscanIP* in Command Prompt
    Affected if The installation folder cannot be found or ThermoscanIP is not installed on this system
  2. Verify the installed version matches the affected version
    Check the version of ThermoscanIP by right-clicking the executable (ThermoscanIP.exe or similar) in the installation folder, selecting Properties, and reviewing the File Version or Product Version field. Compare against version 20211103
    Affected if The installed version is 20211103
  3. Review ACLs on the ThermoscanIP installation folder
    Right-click the installation folder in Windows Explorer, select Properties, go to the Security tab, and examine the permissions for Users and other standard user accounts. Alternatively, run icacls "<installation_path>" in Command Prompt to view all ACL entries
    Affected if The Users group or standard non-admin users are listed with Modify, Write, or Full Control permissions on the installation folder
  4. Check write access to executable files
    Run icacls "<installation_path>\*.exe" to list permissions on executables in the folder. Verify if Users orAuthenticated Users have write (W) or modify permissions to .exe files
    Affected if Non-admin user accounts have Write or Modify permissions on any executable (.exe) files in the ThermoscanIP installation folder
  5. Identify the service account running ThermoscanIP
    Open Services (services.msc), locate the ThermoscanIP service, right-click and select Properties, and check the Log On As account. This account should be a dedicated service account with limited privileges, not LocalSystem or a domain admin account
    Affected if The service runs under LocalSystem, a privileged domain account, or an account with administrative rights

A system is affected if ThermoscanIP version 20211103 is installed AND non-privileged local users have write or modify permissions on the installation folder or its executable files, allowing potential privilege escalation to the service account context.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict permissions on the ThermoscanIP installation folder to follow least-privilege principles: remove write access for non-admin users, ensure only authorized service accounts have modify permissions, and verify executable files are not writable by low-privilege users.

Fix this in Thermoscan Ip Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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