CVE-2023-34982
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 · uneditedThis external control vulnerability, if exploited, could allow a local OS-authenticated user with standard privileges to delete files with System privilege on the machine where these products are installed, resulting in denial of service.
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 confidenceThis is a local privilege escalation vulnerability where a standard OS-authenticated user can delete files that require System privileges, leading to denial of service. The vulnerability involves external control (user-supplied input) improperly influencing file deletion operations.
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< 2020= 2020< 2020= 2020<= 20.1.101<= 3.7.002< 2020= 2020< 2020= 2020< 2020= 2020< 2020= 2020CVSS 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 installed Aveva productCheck Windows installed programs list or look for Aveva installation directories (commonly under C:\Program Files\Aveva\ or C:\ProgramData\Aveva\)Affected if Any Aveva product from the affected list is installed
-
Determine installed versionOpen Windows Programs and Features, locate the Aveva product, and note the version column; or check the product's About dialog if the application is accessibleAffected if Version matches < 2020, = 2020, or <= 20.1.101 (for Aveva Edge), or <= 3.7.002 (for Aveva Enterprise Licensing)
-
Verify running service or applicationOpen Services.msc or Task Manager and check if the Aveva application/service is currently runningAffected if The vulnerable Aveva service or application is active
-
Check file deletion permissions for standard usersUse icacls command on Aveva installation directories (e.g., icacls 'C:\Program Files\Aveva\*') to inspect permissions, specifically looking for Delete or Delete Subfolders and Files rights granted to Users or standard authenticated usersAffected if Standard (non-admin) users have Delete or Delete Subfolders and Files permissions on system-privileged Aveva directories or files
-
Test file deletion as standard userCreate a test file in the Aveva directory using an admin account, then attempt to delete it using a standard user account (or use runas /user:standarduser cmd to verify)Affected if A standard user can successfully delete files that should require elevated privileges
You are affected if a standard OS user can delete files in Aveva installation directories that normally require System privileges, and your installed Aveva product version falls within the affected ranges.
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.
From vendor data2020
Restrict file system permissions to prevent standard users from deleting System-privileged files, and apply vendor patches when available. Validate and sanitize any user input that influences file paths.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34982 — 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-2023-34982 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