CVE-2021-43325
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 · uneditedAutomox Agent 33 on Windows incorrectly sets permissions on a temporary directory. NOTE: this issue exists because of a CVE-2021-43326 regression.
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 confidenceAutomox Agent version 33 for Windows sets insecure permissions on a temporary directory, potentially allowing unprivileged users to access or modify files in that directory. This could enable local privilege escalation or code execution in certain contexts. The vulnerability is a regression from CVE-2021-43326.
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= 33CVSS 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.
-
Confirm Automox Agent is installedOpen Windows Services (services.msc) and look for a service named 'Automox Agent' or check Programs and Features for Automox softwareAffected if Automox Agent is not present on the system, the vulnerability does not apply
-
Identify Automox Agent versionCheck the installed version of Automox Agent via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Automox Agent (DisplayVersion value), or right-click the service in Services and select PropertiesAffected if Version is exactly 33, the system is potentially affected
-
Locate Automox temporary directoryExamine the Automox Agent process or service configuration for paths used for temporary file storage; check environment variables or look for temp folders created by the Automox serviceAffected if A temp directory exists and is owned/created by the Automox Agent service account
-
Verify directory permissions are insecureRight-click the identified temp folder in Windows Explorer, select Properties, then Security tab; check if Users group or unprivileged accounts have Modify or Full Control permissions rather than Read-only accessAffected if Unprivileged users (such as the Users group) have Write, Modify, or Full Control permissions on the Automox temp directory, indicating the vulnerability is present
The system is affected if Automox Agent version 33 is installed AND unprivileged users have write access to its temporary directory, allowing potential privilege escalation.
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 dataApply the vendor patch for CVE-2021-43325 to remediate the temporary directory permission misconfiguration in Automox Agent 33.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43325 — 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-2021-43325 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