CVE-2022-36122
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 · uneditedThe Automox Agent before 40 on Windows incorrectly sets permissions on key files.
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 confidenceThe Automox Agent for Windows versions prior to 40 sets overly permissive file permissions on critical system files, which could allow local unprivileged users to modify or replace these files, potentially leading to privilege escalation.
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< 40CVSS 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.
-
Verify Automox Agent is installedOpen Services (services.msc) and look for 'Automox Agent' service, or check Programs and Features for Automox AgentAffected if Automox Agent is not installed on the system
-
Determine installed Automox Agent versionRun 'wmic product get name,version' or check Programs and Features for the Automox Agent version entryAffected if Version is less than 40 (e.g., 39.x, 38.x, etc.)
-
Check Automox Agent service executable permissionsLocate the Automox Agent executable (typically in C:\Program Files\Automox or C:\Program Files (x86)\Automox), right-click properties, go to Security tab, and verify which users have Write or Modify permissionsAffected if Non-administrator users or the 'Users' group have Write or Modify permissions to the Automox Agent directory or executable
-
Inspect Automox Agent configuration directory permissionsCheck permissions on the Automox Agent data/configuration directory (commonly in %ProgramData%\Automox) using icacls or file properties Security tabAffected if Non-privileged users have permissions to modify files in the configuration or data directories
The environment is affected if Automox Agent version is below 40 AND non-administrator users have write or modify permissions to Automox Agent executables, configuration, or data files.
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 · scoped40
Upgrade the Automox Agent to version 40 or later to apply the corrected file permissions.
Automox Agent version 40
- Download the latest Automox Agent version 40 or later from your Automox administrator console or portal
- Uninstall the current Automox Agent from the Windows system
- Install the Automox Agent version 40 or later on the Windows system
- Verify the installation completed successfully by checking the agent status in the Automox console
- Confirm the agent is properly connecting and reporting to the Automox management platform
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36122 — 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-2022-36122 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