dbcve.org
Snow Inventory AgentApplication · Snowsoftware

CVE-2024-1149

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to 6.7.2 / 6.14.5 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
Improper Verification of Cryptographic Signature vulnerability in Snow Software Inventory Agent on MacOS, Snow Software Inventory Agent on Windows, Snow Software Inventory Agent on Linux allows File Manipulation through Snow Update Packages.This issue affects Inventory Agent: through 6.12.0; Inventory Agent: through 6.14.5; Inventory Agent: through 6.7.2.

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

Improper Verification of Cryptographic Signature vulnerability in Snow Software Inventory Agent across MacOS, Windows, and Linux allows attackers to manipulate files through crafted Snow Update Packages due to the agent's failure to properly validate cryptographic signatures on update packages.

MitigationUpdate Snow Software Inventory Agent to a patched version beyond the affected releases (6.12.0, 6.14.5, 6.7.2) and ensure update packages are sourced only from trusted, legitimate channels.

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
Snow Inventory AgentApplication
Affected:< 6.7.2>= 6.14.0, < 6.14.5= 6.12.0

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Determine Snow Inventory Agent version on Windows
    Open Command Prompt and run: reg query "HKLM\SOFTWARE\Snow Software\Snow Inventory Agent" /v Version
    Affected if The reported version falls within < 6.7.2, = 6.12.0, or >= 6.14.0 but < 6.14.5
  2. Determine Snow Inventory Agent version on Linux
    Run: /opt/snow/snow-reconciliation-agent --version OR check the installed package: dpkg -l | grep snow-inventory-agent (Debian) or rpm -qi snow-inventory-agent (RHEL)
    Affected if The reported version falls within < 6.7.2, = 6.12.0, or >= 6.14.0 but < 6.14.5
  3. Determine Snow Inventory Agent version on macOS
    Run: /Library/Application Support/Snow/SnowInventoryAgent --version OR check the installed package: pkgutil --info com.snowsoftware.SnowInventoryAgent
    Affected if The reported version falls within < 6.7.2, = 6.12.0, or >= 6.14.0 but < 6.14.5
  4. Verify update package functionality is configured
    Check if the agent has an update configuration file (typically snow-update.conf or similar in the agent config directory) and if auto-update or scheduled update checks are enabled
    Affected if The agent is configured to receive or process update packages from remote sources, making it vulnerable to malicious crafted packages

If the installed Snow Inventory Agent version is 6.12.0, or falls below 6.7.2, or is between 6.14.0 and 6.14.4 inclusive, and the agent is configured to process update packages, the environment is affected by this signature validation vulnerability.

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 6.7.2 / 6.14.5 or later
Fixed in 6.7.26.14.5
Interim mitigation

Update Snow Software Inventory Agent to a patched version beyond the affected releases (6.12.0, 6.14.5, 6.7.2) and ensure update packages are sourced only from trusted, legitimate channels.

Recommended fix Moderate confidence

Upgrade to Snow Inventory Agent 6.7.2, 6.14.5, or a version higher than 6.12.0 based on your current branch

  1. 1. Identify the currently installed Snow Inventory Agent version by checking the agent status or configuration
  2. 2. Determine which version branch is currently in use (6.7.x, 6.12.x, or 6.14.x)
  3. 3. For version 6.7.x and below: upgrade to version 6.7.2 or later
  4. 4. For version 6.12.0: upgrade to a version higher than 6.12.0 (such as the next stable 6.12.x release)
  5. 5. For versions 6.14.0-6.14.4: upgrade to version 6.14.5 or later
  6. 6. Verify the upgrade was successful by checking the agent version after installation
  7. 7. Test that the agent can receive and validate update packages correctly

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

Fix this in Snow Inventory Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1149 — 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-2024-1149 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