LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19987: D-Link DIR-822 Rev.B 202KRb06, DIR-822 Rev.C 3.10B06, DIR-860L Rev.B 2.03.B03, DIR-868L Rev.B 2.05B02, DIR-...

D-Link DIR-822 Rev.B 202KRb06, DIR-822 Rev.C 3.10B06, DIR-860L Rev.B 2.03.B03, DIR-868L Rev.B 2.05B02, DIR-880L Rev.A 1.20B01_01_i3se_BETA, and DIR-890L Rev.A 1.21B02_BETA devices mishandle IsAccessPoint in /HNAP1/SetAccessPointMode. In the SetAccessPointMode.php source code, the IsAccessPoint parameter is saved in the ShellPath script file without any regex checking. After the script file is executed, the command injection occurs. A vulnerable /HNAP1/SetAccessPointMode XML message could have shell metacharacters in the IsAccessPoint 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

Several D-Link router firmware versions can mishandle an access-point mode setting so attacker-controlled text may be executed by the device shell. This is a serious network-device risk because successful abuse could affect router control. The supplied sources do not name a vendor patch, CVSS score, or confirmed active exploitation.

Executive priority

Treat as high priority if affected routers remain in service, especially at branch, office, or remote-access edges. The issue targets infrastructure that can influence traffic and access. Prioritize inventory, management-surface restriction, and vendor-supported remediation or replacement.

Technical view

CVE-2018-19987 is command injection in /HNAP1/SetAccessPointMode. SetAccessPointMode.php stores the IsAccessPoint XML value in a ShellPath script without regex validation; when executed, shell metacharacters can trigger command execution. Listed firmware includes DIR-822, DIR-860L, DIR-868L, DIR-880L, and DIR-890L revisions.

Likely exposure

Exposure is limited to the specific D-Link models and firmware versions listed in the CVE source bundle. Internet-facing or broadly reachable router administration surfaces would increase business risk, but the bundle does not state authentication requirements or default exposure.

Exploitation context

The bundle includes a public GitHub reference and describes injection through a crafted HNAP XML field. It does not provide KEV status or another cited source confirming active exploitation, so active exploitation should not be claimed from this evidence.

Researcher notes

Evidence is thin: the CVE text gives vulnerable handlers, parameters, affected versions, and a public reference, but no CVSS, CWE, authentication context, patch identifier, or exploitation confirmation. Validate against actual firmware and vendor advisories before drawing broader exposure conclusions.

Mitigation direction

  • Inventory D-Link routers and compare model, hardware revision, and firmware to the affected list.
  • Check D-Link guidance for fixed firmware, replacement advice, or supported mitigations.
  • Restrict router management interfaces to trusted administrative networks only.
  • Disable remote administration where it is enabled and not required.
  • Replace unsupported affected routers if no vendor-supported fix exists.

Validation and detection

  • Confirm whether any assets match the affected model and firmware revisions.
  • Review router management exposure from internal, guest, and external network paths.
  • Check vendor documentation for firmware status before marking remediation complete.
  • Review device logs for unexpected configuration changes or management activity.
  • Track CVE-2018-19987 separately from adjacent CVE-2018-19986 through CVE-2018-19990 issues.
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.

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-2018-19987 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.