CVE-2022-33937
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 · uneditedDell GeoDrive, Versions 1.0 - 2.2, contain a Path Traversal Vulnerability in the reporting function. A local, low privileged attacker could potentially exploit this vulnerability, to gain unauthorized delete access to the files stored on the server filesystem, with the privileges of the GeoDrive service: NT AUTHORITY\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 confidenceDell GeoDrive versions 1.0-2.2 contain a path traversal vulnerability in the reporting function that allows a local low-privileged attacker to manipulate file paths using '..' sequences, enabling unauthorized deletion of files anywhere on the server filesystem with NT AUTHORITY\SYSTEM privileges.
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< 2.2.3CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 if Dell GeoDrive is installedCheck for Dell GeoDrive installation by searching for the program in Windows installed programs (Control Panel > Programs and Features) or check common installation directories such as C:\Program Files\Dell\GeoDrive or C:\Program Files (x86)\Dell\GeoDriveAffected if Dell GeoDrive software is found on the system
-
Determine installed GeoDrive versionRight-click on the GeoDrive executable (typically geodrive.exe or similar) in the installation folder, select Properties, and view the Version tab. Alternatively, open GeoDrive and check About or Help > About for the version numberAffected if Installed version is 2.2.3 or lower (versions 1.0 through 2.2 are explicitly vulnerable)
-
Verify reporting function accessibilityLocate the reporting module or feature within the GeoDrive application interface. Check if the reporting functionality is exposed via a web service, local executable, or API endpoint. Look for files related to reporting such as report.exe, reporting.dll, or similar in the installation directoryAffected if The reporting function exists and is accessible to local users (even low-privileged accounts)
-
Check process privileges when reporting runsObserve the Dell GeoDrive service process properties in Windows Task Manager or Services console. Note the account context under which the GeoDrive service or reporting component executesAffected if The service runs with elevated privileges (NT AUTHORITY\SYSTEM as noted in the CVE)
A system is affected if Dell GeoDrive versions 1.0 through 2.2 (versions below 2.2.3) are installed with the reporting function enabled and running with SYSTEM privileges, allowing a local attacker to exploit path traversal.
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 · scoped2.2.3
Apply vendor-supplied patch or update to a fixed version of Dell GeoDrive. Until patched, restrict or disable the reporting function and limit local access to trusted administrators only.
Dell GeoDrive 2.2.3
- Inventory all systems running Dell GeoDrive versions 1.0 - 2.2
- Prioritize remediation for systems with exposure to untrusted input paths
- Obtain Dell GeoDrive version 2.2.3 or later from Dell's official support portal (www.dell.com)
- Plan maintenance window and back up critical data
- Apply the upgrade to all affected instances
- Confirm the version upgrade was successful post-installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33937 — 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-33937 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