CVE-2024-31201
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 · uneditedA “CWE-428: Unquoted Search Path or Element” affects the ThermoscanIP_Scrutation service. Such misconfiguration could be abused in scenarios where incorrect permissions were assigned to the C:\ path to attempt a privilege escalation on the local machine.
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 confidenceThe ThermoscanIP_Scrutation service contains an unquoted executable path (CWE-428), causing Windows to search for executables at intermediate path components. If an attacker can write to locations like C:\ThermoscanIP_Scrutation\ or other unquoted path segments due to overly permissive ACLs on the C:\ drive, they could place a malicious executable that gets executed by the service, resulting in privilege escalation to the service account.
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= 20211103CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ThermoscanIP_Scrutation service existsOpen Services console (services.msc) or run: sc query ThermoscanIP_ScrutationAffected if The service does not exist (then not affected)
-
Get the service executable pathRun: sc qc ThermoscanIP_Scrutation and examine the BINARY_PATH_NAME field, or use: wmic service where "name='ThermoscanIP_Scrutation'" get pathnameAffected if The BINARY_PATH_NAME contains spaces and is NOT enclosed in quotation marks
-
Confirm the service is running or configured to runRun: sc query ThermoscanIP_Scrutation and check the STATE, or view in Services consoleAffected if The service is in a running or start-pending state (vulnerability requires the service to execute the path)
-
Check installed product versionCheck the program version in Add/Remove Programs or the installation directory for Proges Thermoscan Ip, version 20211103Affected if The installed version is exactly 20211103 (the affected version)
-
Verify permissions on path directoriesUse icacls or AccessChk on C:\ThermoscanIP_Scrutation\ and intermediate directories (such as C:\) to check for weak ACLs allowing non-admin users to create filesAffected if Non-privileged users have write permissions to any directory in the unquoted path
User is affected if Proges Thermoscan Ip version 20211103 is installed, the ThermoscanIP_Scrutation service exists with an unquoted path containing spaces, and weak permissions allow unauthorized file creation in any path component.
Generated from the published advisory. Verify against your own configuration.
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 dataQuote the service executable path in the service configuration and audit/restrict permissions on the C:\ drive and all directories in the service path to prevent unauthorized file placement.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-31201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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