dbcve.org
GeodriveApplication · Dell

CVE-2022-33918

MEDIUM · 5.5 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 2.2.3 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
Dell GeoDrive, Versions 2.1 - 2.2, contains an information disclosure vulnerability. An authenticated non-admin user could potentially exploit this vulnerability and gain access to sensitive information.

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

Dell GeoDrive versions 2.1-2.2 contains an information disclosure vulnerability where an authenticated non-admin user can gain access to sensitive information they should not be authorized to view, likely due to improper access control or authorization checks in the application.

MitigationImplement proper role-based access control (RBAC) and ensure all sensitive data endpoints enforce authorization checks regardless of user authentication status, restricting non-admin users from accessing privileged information.

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
GeodriveApplication
Affected:>= 2.1.0, < 2.2.3

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Determine installed Dell GeoDrive version
    Check the application version through its UI, about dialog, or version file typically found in the installation directory
    Affected if The installed version is 2.1.0 through 2.2.2 inclusive (versions >= 2.1.0 and < 2.2.3)
  2. Verify multi-user authentication is configured
    Check if the application has user accounts with role-based access (admin vs non-admin roles) configured in the user management settings or authentication configuration
    Affected if Multiple user roles exist and non-admin authenticated users can access the application
  3. Confirm non-admin user accounts exist
    Review the user list or directory to identify if any non-administrator user accounts have been created in the system
    Affected if There are authenticated non-admin users in the system who have access to the application
  4. Inspect access control configuration
    Examine the application configuration files or permission settings to verify whether sensitive data endpoints enforce authorization checks beyond simple authentication
    Affected if Authorization checks are missing or improperly enforced for non-admin users accessing sensitive information

You are affected if Dell GeoDrive version 2.1.0 through 2.2.2 is installed and the application has non-admin user accounts that could potentially access sensitive information they should not be authorized to view.

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

Implement proper role-based access control (RBAC) and ensure all sensitive data endpoints enforce authorization checks regardless of user authentication status, restricting non-admin users from accessing privileged information.

Recommended fix High confidence

Geodrive 2.2.3 or later

  1. Identify the currently installed Geodrive version using the application's version check or system information
  2. Backup any critical data stored in or managed by Geodrive
  3. Download Geodrive version 2.2.3 or later from the official Dell support website (support.dell.com)
  4. Run the installer for the new version and follow the on-screen upgrade instructions
  5. Restart the Geodrive service if prompted
  6. Verify the installation was successful by checking the new version number
Caveat No breaking changes mentioned in the advisory; upgrade is a standard version progression

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

Fix this in Geodrive Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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