dbcve.org
Snow Inventory AgentApplication · Snowsoftware

CVE-2024-1150

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to 7.3.1 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 Unix allows File Manipulation through Snow Update Packages.This issue affects Inventory Agent: through 7.3.1.

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 Snow Software Inventory Agent on Unix versions through 7.3.1 fails to properly verify cryptographic signatures on update packages. This improper signature validation allows an attacker to manipulate files on the target system by crafting malicious Snow Update Packages that the agent will accept without valid cryptographic verification.

MitigationUpgrade the Inventory Agent to a version beyond 7.3.1 that properly validates cryptographic signatures of update packages before processing. If no patched version is available, implement network-level controls to ensure update packages are sourced only from trusted, integrity-protected 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:< 7.3.1

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. Identify the installed Snow Inventory Agent version
    Run the agent binary with version flag (such as --version, -v, or version command) or query the installed package manager for snow-inventory-agent
    Affected if The reported version is 7.3.1 or lower (any version < 7.3.1)
  2. Confirm the agent is configured for updates
    Inspect the agent configuration files for update-related settings, such as update server URL, auto-update intervals, or scheduled update tasks
    Affected if Update functionality is enabled and points to an update server or uses local update packages
  3. Check for presence of update package directories
    Locate the agent's update package storage directory (commonly under /var/opt/snow or the agent's home directory) and list any stored update packages
    Affected if Update packages exist in the agent's designated directory and the agent processes them automatically
  4. Verify update signature validation configuration
    Review the agent configuration for settings controlling signature verification behavior, such as allow unsigned updates or signature verification flags
    Affected if Signature validation is disabled, set to optional, or not enforced on incoming update packages
  5. Check agent logs for update activity
    Examine agent log files for recent update download or installation events, noting any signature validation errors or warnings
    Affected if Updates have been processed without signature validation failures being logged or enforced

The environment is affected if the Snow Inventory Agent version is below 7.3.1 and the update mechanism is configured or has been used to process packages.

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 7.3.1 or later
Fixed in 7.3.1
Interim mitigation

Upgrade the Inventory Agent to a version beyond 7.3.1 that properly validates cryptographic signatures of update packages before processing. If no patched version is available, implement network-level controls to ensure update packages are sourced only from trusted, integrity-protected channels.

Recommended fix Moderate confidence

Snow Inventory Agent 7.3.1 or later

  1. 1. Identify all Snow Inventory Agent installations running on Unix systems in your environment
  2. 2. Verify the current version of each installation using 'snowagent --version' or checking the agent binary
  3. 3. Download Snow Inventory Agent version 7.3.1 or later from the official Snow Software portal or your licensed distribution channel
  4. 4. Plan the upgrade during a maintenance window to minimize business impact
  5. 5. Upgrade the agent on each Unix system using standard package management tools (e.g., dpkg, rpm, or the provided installer)
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Confirm the agent is functioning normally by checking that it can communicate with the Snow Management Center
Caveat Review Snow Software release notes for any configuration or behavioral changes between your current version and 7.3.1

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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