CVE-2024-25958
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 Grab for Windows, versions up to and including 5.0.4, contain Weak Application Folder Permissions vulnerability. A local authenticated attacker could potentially exploit this vulnerability, leading to privilege escalation, unauthorized access to application data, unauthorized modification of application data and service disruption.
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 confidenceDell Grab for Windows versions up to 5.0.4 have weak NTFS permissions on the application folder, allowing authenticated local users to modify executable files, configuration files, and application data. This permission misconfiguration enables privilege escalation by allowing standard users to replace application binaries with malicious ones or modify service configurations.
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< 5.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Dell Grab installationCheck for Dell Grab installation directory in common locations (e.g., C:\Program Files\Dell\Grab, C:\Program Files (x86)\Dell\Grab) or search for the executable file named 'Dell Grab.exe' or similar Dell Grab executables using Get-ChildItem or dir command.Affected if Dell Grab is installed on the system
-
Identify installed versionRight-click on the Dell Grab executable file in the installation folder, select Properties, and view the 'Details' tab to find the File Version. Alternatively, open PowerShell and run: Get-Item 'C:\Path\To\DellGrab.exe' | Select-Object VersionInfoAffected if The installed version is any version prior to 5.0.5 (e.g., 5.0.4, 5.0.3, etc.)
-
Check NTFS permissions on installation folderOpen Command Prompt or PowerShell and run: icacls 'C:\Path\To\DellGrabFolder' (replace with actual installation path). Look for entries showing 'Users' or specific standard user accounts with (F) Full Control, (M) Modify, or (W) Write permissions.Affected if Authenticated Users, Users group, or standard user accounts have Write, Modify, or Full Control permissions on the Dell Grab installation folder
-
Verify executable file permissionsRun: icacls 'C:\Path\To\DellGrabFolder\*.exe' to list permissions on executable files in the installation directory. Check if non-admin users can modify or replace these files.Affected if Standard users have permission to modify, write, or delete executable files in the Dell Grab folder
-
Check configuration and data file permissionsRun: icacls 'C:\Path\To\DellGrabFolder\*' | findstr /i "Users" to identify if standard users can modify configuration files (.config, .xml, .ini) or application data files stored in the installation directory.Affected if Configuration files or application data files are writable by standard (non-admin) users
If Dell Grab versions prior to 5.0.5 are installed AND standard users have Write/Modify permissions on the application folder or its executables/config files, the environment is vulnerable to local privilege escalation via this permission misconfiguration.
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 · scoped5.0.5
Restrict folder permissions on the Dell Grab installation directory to administrators and the SYSTEM account, removing write access for standard users. Verify that application data folders have appropriate access controls and consider implementing application folder integrity monitoring.
Version 5.0.5 or later
- Back up any important data or configurations from the current Grab installation
- Download Dell Grab version 5.0.5 or later from the official Dell support website (www.dell.com)
- Uninstall the current version of Dell Grab for Windows
- Install the new version (5.0.5 or later) with default permissions
- Verify that the application folder permissions are correctly configured after installation
- Test that the application functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25958 — 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-25958 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