CVE-2022-24387
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 · uneditedWith administrator or admin privileges the application can be tricked into overwriting files in app_data/Config folder, e.g. the systemsettings.xml file. THis is possible in SmarterTrack v100.0.8019.14010
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 confidenceAn authenticated file write vulnerability in SmarterTrack v100.0.8019.14010 allows users with administrator privileges to overwrite files in the app_data/Config folder, such as systemsettings.xml, potentially leading to code execution or further system compromise.
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>= 100.0.8019, < 100.0.8075CVSS 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify SmarterTrack installation pathCheck common installation directories such as C:\Program Files\SmarterTools\SmarterTrack or look for the SmarterTrack service in Windows Services.Affected if SmarterTrack is installed on the system
-
Determine installed SmarterTrack versionLocate the version information in the installation directory. Typically found in a version.dll, AssemblyInfo.cs, or check the Windows Service properties for SmarterTrack. The version format is typically 100.0.xxxxx.x.Affected if The installed version matches 100.0.8019 or higher, but is lower than 100.0.8075
-
Verify app_data/Config directory existsCheck for the presence of the app_data/Config folder within the SmarterTrack installation directory. This folder normally contains systemsettings.xml and other configuration files.Affected if The app_data/Config directory exists in the SmarterTrack installation path
The system is affected if SmarterTrack is installed with a version between 100.0.8019 and 100.0.8074 (inclusive), as this version range allows authenticated administrators to overwrite configuration files in the app_data/Config folder.
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.
dbcve · scoped100.0.8075
Upgrade to a patched version of SmarterTrack. If immediate patching is not feasible, restrict administrative access and implement file integrity monitoring on the app_data/Config directory.
Smartertrack version 100.0.8075 or later
- Backup the current Smartertrack installation and database
- Download Smartertrack version 100.0.8075 or later from the official vendor
- Install the upgrade following the vendor's documented upgrade procedure
- Verify that the app_data/Config folder no longer allows arbitrary file overwriting via the vulnerable endpoint
- Confirm the systemsettings.xml file cannot be overwritten through the file upload mechanism
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24387 — 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-2022-24387 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