CVE-2022-27904
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 for macOS before version 39 was vulnerable to a time-of-check/time-of-use (TOCTOU) race-condition attack during the agent install process.
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 for macOS versions prior to 39 contained a time-of-check/time-of-use (TOCTOU) race condition during the installation process. An attacker with local access could potentially exploit the window between security checks and file operations to manipulate installation files, possibly achieving privilege escalation or code execution.
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< 39CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 for macOS is installedCheck for the presence of Automox Agent by querying installed packages: run 'pkgutil --pkgs | grep -i automox' in Terminal, or look for Automox Agent.app in /Applications/Affected if No Automox Agent for macOS is found on the system, the check does not apply
-
Retrieve the installed Automox Agent versionRun 'defaults read /Applications/Automox\ Agent.app/Contents/Info CFBundleVersion' or use 'pkgutil --pkg-info com.automox.agent' to query the package version from installation receiptsAffected if The version returned is less than 39, or the version cannot be determined (indicating an older installation that predates version tracking)
-
Confirm vulnerability applicabilityCompare the installed version number against the affected range: versions prior to 39 are vulnerableAffected if The installed version is below 39
The system is affected if Automox Agent for macOS is installed and its version is less than 39.
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 · scoped39
Upgrade Automox Agent for macOS to version 39 or later to remediate this vulnerability.
Automox Agent for macOS version 39
- Download the Automox Agent installer for macOS from the official Automox portal or management console
- Locate the installer package (.pkg file) and double-click to initiate the installation
- Follow the on-screen prompts to complete the installation process
- Verify the agent is running and connected to the Automox management console
- Confirm the installed version is 39 or higher by checking the agent details in the Automox console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27904 — 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-27904 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