LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19989: In the /HNAP1/SetQoSSettings message, the uplink parameter is vulnerable, and the vulnerability affects D-L...

In the /HNAP1/SetQoSSettings message, the uplink parameter is vulnerable, and the vulnerability affects D-Link DIR-822 Rev.B 202KRb06 and DIR-822 Rev.C 3.10B06 devices. In the SetQoSSettings.php source code, the uplink parameter is saved in the /bwc/entry:1/bandwidth and /bwc/entry:2/bandwidth internal configuration memory without any regex checking. And in the bwc_tc_spq_start, bwc_tc_wfq_start, and bwc_tc_adb_start functions of the bwcsvcs.php source code, the data in /bwc/entry:1/bandwidth and /bwc/entry:2/bandwidth is used with the tc command without any regex checking. A vulnerable /HNAP1/SetQoSSettings XML message could have shell metacharacters in the uplink element such as the `telnetd` string.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Specific D-Link DIR-822 router firmware versions accept an unsafe QoS setting that can later be used in an operating-system command. If an attacker can reach the affected HNAP management function, the issue could allow device-level command execution. The public sources do not provide CVSS, patch status, or evidence of active exploitation.

Executive priority

Treat this as a priority for perimeter and branch-office router review. The affected devices are narrow, but command execution on network equipment can undermine traffic control and provide a foothold. Urgency depends on whether these models are deployed and reachable from untrusted networks.

Technical view

CVE-2018-19989 affects D-Link DIR-822 Rev.B 202KRb06 and Rev.C 3.10B06. The /HNAP1/SetQoSSettings uplink value is stored in internal bandwidth configuration without regex validation, then reused by bwcsvcs.php functions in a tc command path without validation, creating command-injection risk.

Likely exposure

Exposure is most likely where affected DIR-822 Rev.B or Rev.C devices run the named firmware and the HNAP management interface is reachable by untrusted users or networks. The sources do not establish whether authentication is required or whether other revisions are affected.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source confirms exploitation in the wild. Public reference material describes the vulnerable parameter and code path, but the bundle does not provide verified attacker prerequisites, exploit reliability, or patch availability.

Researcher notes

Evidence is limited to the CVE description and linked public research reference. Key unknowns are authentication requirements, default exposure, affected firmware lineage, and vendor remediation status. Do not broaden affected products beyond DIR-822 Rev.B 202KRb06 and Rev.C 3.10B06 without additional evidence.

Mitigation direction

  • Inventory D-Link DIR-822 Rev.B and Rev.C devices and firmware versions.
  • Restrict router management and HNAP access to trusted administration networks.
  • Check D-Link guidance for fixed firmware or retirement recommendations.
  • Replace or isolate affected devices if vendor support is unavailable.
  • Monitor router configuration changes and unexpected management access.

Validation and detection

  • Confirm whether any DIR-822 Rev.B 202KRb06 devices are deployed.
  • Confirm whether any DIR-822 Rev.C 3.10B06 devices are deployed.
  • Verify HNAP and management interfaces are not internet exposed.
  • Review router logs for unexpected QoS or management changes.
  • Compare deployed firmware against current vendor guidance.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2018-19989 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
2Source 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.