D-Link is asking DGS-3130-30TS switch operators to disable its discovery protocol before corrective firmware is available. The reported weaknesses could expose configuration and management credentials, permit administrative changes, or disrupt network service. An attacker needs access to the affected network.

The manufacturer’s November 6 interim advisory, SAP10523, credits Giresh Kumar Enugu of Spectrum Community Solutions. Sergiu Gatlan’s BleepingComputer report covers the warning. D-Link says it received the disclosure on November 2.

Evidence status: researcher-reported exploitation in controlled testing, acknowledged by the vendor. The advisory supplies no evidence of an active attack campaign. It says D-Link is independently investigating the findings and mitigation.

The confirmed test scope is narrower than the product family

D-Link identifies DGS-3130-30TS, hardware revision B1, as the tested product. The examined firmware versions are 2.00.B014, 2.00.B034, 2.04.000 and 2.04.001. Individual findings may affect different subsets of those versions.

Other DGS-3130 models, hardware revisions and D-Link switching platforms remain under investigation. Their inclusion in the investigation does not establish vulnerability. The advisory provides neither a complete affected-version range nor a fixed release.

The main findings concern DDP, the D-Link Discovery Protocol, including authentication, access control and information handling. Possible consequences include unauthorized credential changes, configuration disclosure, resets and exposure of SNMP community strings, shared secrets used for device management.

Separate findings concern SSH configuration, operating-system credential protection and embedded cryptographic material. Turning off discovery does not correct those firmware weaknesses.

Disable DDP, then verify the saved configuration

D-Link recommends these interim measures:

  • Disable DDP globally and on applicable physical interfaces. Follow the advisory and the CLI reference for the installed firmware. Verify the resulting configuration, save it and confirm persistence after a restart. Account for discovery or management workflows that depend on DDP.
  • Remove default and unnecessary SNMP communities. Where management through SNMP is required, use appropriately secured SNMPv3 with authentication and privacy, where supported. Limit access to authorized management hosts.
  • Restrict SSH, web management and SNMP reachability. Keep management services off the public internet, disable unused services and review connected network segments. D-Link warns against relying exclusively on management access controls or VLAN separation for the DDP issues.
  • Preserve verified configuration backups and review unexpected changes. Investigate unexplained credential changes, reboots, interface shutdowns, factory resets or service interruptions through the organization’s incident-response process.

The researcher says disabling DDP globally and at interface level prevented the tested DDP vectors from being processed. D-Link is reviewing that result. Removing SNMP communities alone also leaves the reported DDP disclosure route unresolved.

An existing download is not an announced security fix

As of the advisory’s November 6, 12:30 GMT update, corrective firmware and a release schedule are unavailable. CVE identifiers have not been publicly disclosed.

Track the same advisory for confirmed scope and a validated repair. Before any later upgrade, match the model, hardware revision and installed firmware to D-Link’s instructions. Firmware for another hardware revision may be incompatible. Treat a release as corrective only when D-Link explicitly identifies the applicable fixes.

Caveat: D-Link’s investigation is incomplete; these are interim mitigations for reported findings, not a verified repair of the entire firmware security architecture.