dbcve.org
Resident Download ManagerApplication · Shdesigns

CVE-2016-6567

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SHDesigns' Resident Download Manager provides firmware update capabilities for Rabbit 2000/3000 CPU boards, which according to the reporter may be used in some industrial control and embedded applications. The Resident Download Manager does not verify that the firmware is authentic before executing code and deploying the firmware to devices. A remote attacker with the ability to send UDP traffic to the device may be able to execute arbitrary code on the device. According to SHDesigns' website, the Resident Download Manager and other Rabbit Tools have been discontinued since June 2011.

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

SHDesigns' Resident Download Manager for Rabbit 2000/3000 CPU boards lacks firmware authenticity verification before execution and deployment. A remote attacker sending malicious UDP traffic to the device can inject and execute arbitrary firmware code, achieving full device compromise.

MitigationSince the product is discontinued with no patch available, mitigate by isolating affected devices on restricted network segments, blocking unauthorized UDP traffic at network boundaries, or replacing with actively maintained hardware.

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
Resident Download ManagerApplication
Affected:all versions

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

CVSS:3.0/AV:N/AC:L/PR:N/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 Rabbit 2000/3000 CPU boards running SHDesigns software
    Inventory network devices and check for Rabbit 2000/3000 CPU boards with SHDesigns' Resident Download Manager installed. Consult device documentation or check the firmware/software inventory on the device.
    Affected if The device is a Rabbit 2000/3000 CPU board with SHDesigns Resident Download Manager present.
  2. Confirm the download manager service is active
    On the Rabbit device, check if the Resident Download Manager service or daemon is running. This may be visible in the device's running processes or service list, depending on the OS/configuration.
    Affected if The Resident Download Manager service is running and accessible on the device.
  3. Check for open UDP ports used by download manager
    Scan the device or review network configuration to identify open UDP ports associated with the download manager functionality. Consult SHDesigns documentation for default port numbers or perform a port scan targeting the device.
    Affected if UDP ports used by the download manager are open and listening.
  4. Verify network accessibility of the download manager
    From an external network perspective, attempt to send UDP packets to the device on the identified download manager ports. Determine if the device accepts UDP traffic from unauthorized sources.
    Affected if The device accepts UDP traffic on download manager ports from untrusted network segments.

A user is affected if they have a Rabbit 2000/3000 CPU board running SHDesigns Resident Download Manager with the download service active and accessible via UDP on the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the product is discontinued with no patch available, mitigate by isolating affected devices on restricted network segments, blocking unauthorized UDP traffic at network boundaries, or replacing with actively maintained hardware.

Recommended fix High confidence
  1. Identify all systems running Resident Download Manager, as the product was discontinued in June 2011 and receives no security updates.
  2. Isolate affected devices on a separate network segment with strict firewall rules to limit UDP traffic access.
  3. If possible, remove or uninstall Resident Download Manager entirely from affected systems.
  4. Implement additional network monitoring to detect any suspicious UDP traffic targeting port 7 (or the specific port used by the application).
  5. Consider replacing the discontinued Rabbit Tools firmware update mechanism with an authenticated, integrity-checked solution.
  6. If the affected device cannot be replaced or retired, apply compensating controls such as disabling the firmware update functionality if possible.

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

Fix this in Resident Download Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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