CVE-2024-0353
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 · uneditedLocal privilege escalation vulnerability potentially allowed an attacker to misuse ESET’s file operations to delete files without having proper permission.
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 analysisPrivileges are granted, or fail to be dropped, incorrectly, so an action runs with more power than it should. An attacker who reaches that path inherits the excess privilege. The fix is least-privilege throughout, with explicit, checked transitions whenever privilege changes.
General guidance for the improper privilege management class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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< 8.1.2062.0>= 9.0, < 9.1.2071.0>= 10.0, < 10.0.2052.0>= 10.1, < 10.1.2063.0>= 11.0, < 11.0.2032.0< 8.1.2062.0>= 9.0, < 9.1.2071.0>= 10.0, < 10.0.2052.0>= 10.1, < 10.1.2063.0>= 11.0, < 11.0.2032.0all versions< 17.0.10.0< 7.3.10018.0< 7.3.14006.0>= 8.0, < 8.0.10024.0>= 8.0, < 8.0.14014.0>= 9.0, < 9.0.10012.0>= 9.0, < 9.0.14008.0>= 10.0, < 10.0.10018.0>= 10.0, < 10.0.14007.0>= 10.1, < 10.1.10014.0< 17.0.10.0< 7.3.15006.0< 17.0.10.0>= 8.0, < 8.0.15012.0>= 9.0, < 9.0.15006.0>= 10.0, < 10.0.15005.0< 7.3.12013.0>= 8.0, < 8.0.12016.0>= 9.0, < 9.0.12019.0>= 10.0, < 10.0.12015.0CVSS 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
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 · scoped7.3.10018.07.3.12013.07.3.14006.0
For Endpoint products: upgrade to 8.1.2062.0, 9.1.2071.0, 10.0.2052.0, or 10.1.2063.0 or later depending on your product branch; for Internet Security/Nod32 Antivirus: upgrade to 17.0.10.0 or later; for other products, obtain specific version from ESET support
- 1. Identify the exact ESET product and current version installed on the system using 'msinfo32' or checking Add/Remove Programs
- 2. Determine which product line applies to your installation from: Endpoint Antivirus, Endpoint Security, File Security, Internet Security, Mail Security, Nod32 Antivirus, Security, or Server Security
- 3. Visit the official ESET support portal at support.eset.com and search for CVE-2024-0353 to obtain the specific fixed version for your product line
- 4. Download the latest ESET security product version from official ESET download channels only
- 5. Before upgrading, ensure you have a complete system backup and export your ESET settings
- 6. Run the ESET installer with administrator privileges to apply the update
- 7. Verify the installation completed successfully and confirm the new version matches the fixed release
- 8. Restart the computer if prompted to ensure all security components load correctly
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0353 — 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-0353 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