LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19066: An issue was discovered on Foscam C2 devices with System Firmware 1.11.1.8 and Application Firmware 2.72.1....

An issue was discovered on Foscam C2 devices with System Firmware 1.11.1.8 and Application Firmware 2.72.1.32, and Opticam i5 devices with System Firmware 1.5.2.11 and Application Firmware 2.21.1.128. The exported device configuration is encrypted with the hardcoded Pxift* password in some cases.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Foscam C2 and Opticam i5 camera firmware versions can export device configuration protected by a hardcoded password. If someone obtains an exported configuration file, the protection may not meaningfully keep device settings or stored secrets confidential. The sources do not provide CVSS, confirmed exploitation, or a named fixed version.

Executive priority

Treat this as a targeted confidentiality risk for affected camera fleets, not as confirmed widespread exploitation. Prioritize inventory and vendor guidance first, then reduce access to camera management paths and clean up stored configuration exports.

Technical view

CVE-2018-19066 covers exported configuration encryption using the hardcoded password “Pxift*” in some cases. Listed versions are Foscam C2 System Firmware 1.11.1.8 / Application Firmware 2.72.1.32 and Opticam i5 System Firmware 1.5.2.11 / Application Firmware 2.21.1.128. The record does not identify a CWE, CVSS vector, patch level, or exploit activity.

Likely exposure

Exposure is most likely where affected camera models are deployed and configuration exports are stored, shared, backed up, or retrievable by unauthorized users. Internet exposure of camera management interfaces would increase concern, but the bundle does not state that network access alone triggers this issue.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not listed as KEV. The practical risk depends on access to exported configuration files and what sensitive values those files contain. Evidence is incomplete on exploit prevalence, vendor remediation, and all affected firmware branches.

Researcher notes

The public record is sparse: no CVSS, CWE, full affected CPE list, exploit evidence, or fixed versions are included. Analysis should remain limited to the named models and firmware versions unless additional vendor or advisory evidence expands scope.

Mitigation direction

  • Inventory Foscam C2 and Opticam i5 devices and record firmware versions.
  • Check vendor guidance for fixed firmware or replacement recommendations.
  • Restrict camera administration access to trusted management networks.
  • Remove unnecessary exported configuration files from shared storage and backups.
  • Rotate credentials or secrets stored in affected configuration exports.
  • Replace unsupported devices if no vendor fix is available.

Validation and detection

  • Confirm whether deployed devices match the affected model and firmware versions.
  • Review file shares, tickets, and backups for exported camera configuration files.
  • Verify camera management interfaces are not exposed to untrusted networks.
  • Document whether vendor firmware or compensating controls are in place.
  • Check credential rotation records for secrets stored in prior exports.
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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. 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-19066 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.