LiveActive security incident?Get immediate response
CVE Record

CVE-2017-18377: An issue was discovered on Wireless IP Camera (P2P) WIFICAM cameras.

An issue was discovered on Wireless IP Camera (P2P) WIFICAM cameras. There is Command Injection in the set_ftp.cgi script via shell metacharacters in the pwd variable, as demonstrated by a set_ftp.cgi?svr=192.168.1.1&port=21&user=ftp URI.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects certain Wireless IP Camera (P2P) WIFICAM devices. A vulnerable camera could let an unauthenticated attacker inject operating-system commands through an FTP settings CGI handler. That can mean full device takeover, but the public record does not provide precise vendor, model, firmware, CVSS, or patch details.

Executive priority

Prioritize finding and isolating exposed devices. The business risk is device takeover and use as a foothold into networks or surveillance infrastructure. Urgency is highest for internet-facing or unsupported cameras.

Technical view

CVE-2017-18377 is command injection in set_ftp.cgi, specifically the FTP password parameter, on Wireless IP Camera (P2P) WIFICAM cameras. The linked research categorizes the issue as pre-auth root remote code execution. Public CVE metadata leaves affected vendor/product/version fields effectively unspecified.

Likely exposure

Exposure is most likely where legacy WIFICAM/P2P IP cameras expose their embedded web interface to LAN, VPN, or the internet. Scope is hard to determine from the CVE record because affected models and firmware versions are not enumerated.

Exploitation context

The CVE is not listed as CISA KEV in the supplied bundle. Public research describes pre-auth root RCE, but the provided sources do not establish active exploitation. Treat internet-facing devices as urgent due to remote command execution potential.

Researcher notes

Evidence supports command injection and reported pre-auth root RCE, but asset matching is weak because the CVE lists no concrete vendor, product, version, CPE, CVSS, or remediation. Validation should focus on fingerprinting deployed devices and confirming exposure without running exploit tests.

Mitigation direction

  • Identify and isolate any WIFICAM/P2P IP cameras in the environment.
  • Remove direct internet exposure to camera web interfaces.
  • Restrict camera management access to trusted admin networks only.
  • Check vendor or reseller firmware guidance for affected models.
  • Replace unsupported devices when no vendor fix is available.
  • Monitor perimeter controls for attempted access to vulnerable CGI paths.

Validation and detection

  • Inventory camera model names, firmware versions, and management URLs.
  • Confirm whether any camera interface is reachable from untrusted networks.
  • Review logs for suspicious requests to set_ftp.cgi and FTP settings changes.
  • Check vendor guidance against discovered firmware versions.
  • Verify firewall rules block unmanaged access to camera web services.
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-2017-18377 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.