LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11481: TP-LINK IPC TL-IPC223(P)-6, TL-IPC323K-D, TL-IPC325(KP)-*, and TL-IPC40A-4 devices allow authenticated remo...

TP-LINK IPC TL-IPC223(P)-6, TL-IPC323K-D, TL-IPC325(KP)-*, and TL-IPC40A-4 devices allow authenticated remote code execution via crafted JSON data because /usr/lib/lua/luci/torchlight/validator.lua does not block various punctuation characters.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes authenticated remote code execution in several TP-LINK IPC camera devices. An attacker with valid access could potentially run code on the device through crafted JSON input. Business urgency depends on whether these models are deployed and reachable, because sources do not provide CVSS, patch status, or confirmed active exploitation.

Executive priority

Treat this as a high-priority exposure check for legacy TP-LINK IPC devices. The impact is serious because code execution could compromise camera infrastructure, but immediate urgency should be driven by deployed model presence, management exposure, credential hygiene, and vendor support status.

Technical view

CVE-2018-11481 affects TP-LINK IPC TL-IPC223(P)-6, TL-IPC323K-D, TL-IPC325(KP)-*, and TL-IPC40A-4 devices. The stated cause is insufficient character filtering in /usr/lib/lua/luci/torchlight/validator.lua, allowing crafted JSON data to reach command execution paths. The public record describes the issue as authenticated RCE.

Likely exposure

Exposure is most likely where the listed TP-LINK IPC devices are still in service, especially if administrative interfaces are reachable from broad internal networks or the internet. The source states authentication is required, so weak, shared, or reused credentials materially increase risk.

Exploitation context

The CVE record references a public GitHub item describing authenticated RCE, but the provided sources do not establish active exploitation. The CVE is not listed as KEV in the supplied bundle. No reliable patch, fixed firmware version, or vendor mitigation is named in the provided evidence.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE mapping, or fixed versions are provided in the bundle. The affected models come from the title and description, while the technical root cause is described as validator.lua failing to block punctuation characters in crafted JSON handling.

Mitigation direction

  • Inventory for the listed TP-LINK IPC models.
  • Check TP-LINK advisories or firmware guidance for supported fixes.
  • Restrict camera management access to trusted administrative networks.
  • Rotate default, shared, or weak device credentials.
  • Retire or isolate unsupported devices if no fix is available.

Validation and detection

  • Confirm whether listed models exist in asset inventory.
  • Verify firmware versions against vendor guidance when available.
  • Review network exposure of camera management interfaces.
  • Check logs for unusual authenticated administrative activity.
  • Confirm segmentation blocks untrusted access to management ports.
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-11481 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.

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.