dbcve.org
Remote CollectorApplication · Device42

CVE-2021-41315

HIGH · 8.8 CVSS v3.1 Published 2021-09-17
Fix available
A fix is available. Upgrade to 17.05.01 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The Device42 Remote Collector before 17.05.01 does not sanitize user input in its SNMP Connectivity utility. This allows an authenticated attacker (with access to the console application) to execute arbitrary OS commands and escalate privileges.

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 · high confidence

This is a command injection vulnerability in Device42 Remote Collector's SNMP Connectivity utility. The application fails to sanitize user input before passing it to OS-level commands, allowing an authenticated attacker to inject and execute arbitrary OS commands. Since the attack grants elevated privileges, a compromised low-privilege account can be used to gain full system control.

MitigationUpgrade Device42 Remote Collector to version 17.05.01 or later. If immediate patching is not possible, restrict console application access to trusted users only and monitor for suspicious SNMP utility usage.

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
Remote CollectorApplication
Affected:< 17.05.01

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify Device42 Remote Collector installation
    Locate the Device42 Remote Collector application on the system. Check common installation directories or use system inventory tools to find the installation path.
    Affected if Device42 Remote Collector is not installed, the system is not affected by this specific CVE.
  2. Determine installed version of Device42 Remote Collector
    Access the application version information, typically available in the application UI, about section, or installed programs list. Compare the version number against the vulnerable range: versions prior to 17.05.01.
    Affected if The installed version is below 17.05.01, the application falls within the vulnerable range.
  3. Verify SNMP Connectivity utility is configured
    Access the Device42 Remote Collector management interface and check whether the SNMP Connectivity utility feature has been enabled or configured. This utility handles SNMP operations and is the vulnerable component.
    Affected if The SNMP Connectivity utility is not present or has never been configured, the specific attack surface may not be accessible.
  4. Review access controls on the SNMP utility
    Examine user accounts and permissions within Device42 Remote Collector, particularly those with access to the SNMP Connectivity utility. Command injection requires an authenticated attacker.
    Affected if Low-privilege or compromised user accounts have access to the SNMP utility, an attacker could leverage this for command injection.

A system is affected if Device42 Remote Collector version is below 17.05.01 and the SNMP Connectivity utility is accessible to authenticated users.

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

Upgrade Device42 Remote Collector to version 17.05.01 or later. If immediate patching is not possible, restrict console application access to trusted users only and monitor for suspicious SNMP utility usage.

Recommended fix High confidence

17.05.01 or later

  1. 1. Identify all Device42 Remote Collector instances currently deployed in your environment
  2. 2. Verify the current version of each Remote Collector installation
  3. 3. For any instance running a version prior to 17.05.01, download the updated Remote Collector version 17.05.01 or later from the official Device42 download portal
  4. 4. Follow the standard Device42 upgrade procedure documented in docs.device42.com for the Remote Collector component
  5. 5. After upgrade, verify the SNMP Connectivity utility now properly sanitizes user input
  6. 6. Confirm the Remote Collector is functioning correctly and communicating with the main Device42 appliance

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

Fix this in Remote Collector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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