dbcve.org
AutomoxApplication

CVE-2022-24308

MEDIUM · 5.5 CVSS v3.1 Published 2022-04-13
Fix available
A fix is available. Upgrade to 36 / 37 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Automox Agent prior to version 37 on Windows and Linux and Version 36 on OSX could allow for a non privileged user to obtain sensitive information during the 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 confidence

The Automox Agent prior to version 37 on Windows/Linux and version 36 on OSX contains an information disclosure vulnerability that allows unprivileged users to obtain sensitive information during the installation process. This local information disclosure has a low attack complexity and requires no privileges but some user interaction.

MitigationUpgrade Automox Agent to version 37 or later for Windows/Linux systems, or version 36 for OSX systems to remediate this vulnerability.

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
AutomoxApplication
Affected:< 36< 37

CVSS 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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Automox Agent is installed
    On Windows: look for 'Automox Agent' service in Services or check for C:\Program Files\Automox\ or C:\Program Files (x86)\Automox\ directories. On Linux: check for /opt/automox or run 'systemctl list-units | grep automox' or 'ps aux | grep automox'. On OSX: check /Applications/ for Automox or run 'ls /Library/LaunchAgents/'
    Affected if Automox Agent is found installed on the system
  2. Determine the Automox Agent version
    On Windows: check the version property of the Automox executable in the installation directory, or run 'wmic product get name,version' if listed. On Linux: run 'rpm -q automox' or 'dpkg -l | grep automox'. On OSX: right-click Automox.app > Get Info or run 'defaults read /Applications/Automox.app/Contents/Info CFBundleVersion'
    Affected if The installed version cannot be determined or is below 37 (Windows/Linux) or below 36 (OSX)
  3. Confirm operating system type
    On Windows: run 'winver' or check system properties. On Linux: run 'uname -a' or check /etc/os-release. On OSX: run 'sw_vers'
    Affected if OS is Windows or Linux and version < 37, or OS is OSX and version < 36 - the system is in the affected version range

The system is affected if Automox Agent is installed and the installed version is below 37 on Windows/Linux or below 36 on OSX, as the information disclosure vulnerability exists in those unpatched versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 36 / 37 or later
Fixed in 3637
Interim mitigation

Upgrade Automox Agent to version 37 or later for Windows/Linux systems, or version 36 for OSX systems to remediate this vulnerability.

Recommended fix High confidence

Automox Agent version 37 for Windows/Linux; version 36 for macOS/OSX

  1. Download the latest Automox Agent installer from the official Automox website or your organization's software distribution point
  2. For Windows and Linux systems: Upgrade to Automox Agent version 37 or later
  3. For macOS/OSX systems: Upgrade to Automox Agent version 36 or later
  4. Verify the installed version matches the expected upgrade version using the agent status command or console

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Automox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24308 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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