LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8408: An issue was discovered on D-Link DCS-1130 devices.

An issue was discovered on D-Link DCS-1130 devices. The device provides a user with the capability of setting a SMB folder for the video clippings recorded by the device. It seems that the GET parameters passed in this request (to test if SMB credentials and hostname sent to the device work properly) result in being passed as commands to a "system" API in the function and thus result in command injection on the device. If the firmware version is dissected using binwalk tool, we obtain a cramfs-root archive which contains the filesystem set up on the device that contains all the binaries. The binary "cgibox" is the one that has the vulnerable function "sub_7EAFC" that receives the values sent by the GET request. If we open this binary in IDA-pro we will notice that this follows a ARM little endian format. The function sub_7EAFC in IDA pro is identified to be receiving the values sent in the GET request and the value set in GET parameter "user" is extracted in function sub_7E49C which is then passed to the vulnerable system API call.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

D-Link DCS-1130 cameras have a reported command-injection flaw in the SMB video clipping configuration test. A crafted value in a request parameter may be passed to a system call on the device. Sources do not provide CVSS, patch status, or active exploitation evidence.

Executive priority

Treat this as an exposure-management issue for legacy IoT cameras. Prioritize discovery, isolation, and replacement planning where DCS-1130 devices remain in use, because patch and exploit evidence is incomplete in the supplied sources.

Technical view

The report describes GET parameters used to test SMB credentials and hostnames reaching cgibox on ARM little-endian firmware. The user parameter is extracted by sub_7E49C, reaches vulnerable function sub_7EAFC, and is passed to a system API, creating command-injection risk.

Likely exposure

Exposure is limited to environments still running D-Link DCS-1130 devices, especially where camera administration or SMB configuration endpoints are reachable. The source bundle does not confirm affected firmware versions, authentication requirements, or Internet exposure conditions.

Exploitation context

No provided source states active exploitation, and the CVE is not marked KEV. Public references describe vulnerability research and binary analysis, but the bundle does not provide a vendor advisory, exploit status, or remediation timeline.

Researcher notes

The strongest technical evidence is the described firmware and cgibox reverse-engineering path. The bundle lacks firmware-version boundaries, proof of authentication state, CVSS metrics, and vendor remediation. Avoid assuming broader D-Link impact beyond DCS-1130.

Mitigation direction

  • Inventory D-Link DCS-1130 cameras and record firmware versions.
  • Restrict camera administration interfaces to trusted management networks.
  • Remove direct Internet access to affected cameras.
  • Check D-Link or support-channel guidance for firmware updates or retirement advice.
  • Replace unsupported devices if no maintained firmware is available.

Validation and detection

  • Confirm whether any D-Link DCS-1130 devices exist in the environment.
  • Review firewall and ACL rules protecting camera management interfaces.
  • Check camera configuration for SMB video clipping usage.
  • Look for logs showing unexpected configuration-test requests.
  • Document firmware versions and vendor support status.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-8408 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.