Security readout for executives and security teams
Plain-English summary
CVE-2017-2857 affects Foscam C1 Indoor HD Cameras with DDNS enabled. If an attacker can intercept the camera's HTTP connections, they may cause a buffer overflow and fully compromise the device. The sources rate this high severity, but do not show CISA KEV listing or active exploitation evidence.
Executive priority
Treat as high priority for any deployed Foscam C1 cameras, particularly in security-sensitive sites. The main business risk is full device compromise, which can affect surveillance integrity and provide a foothold in poorly segmented networks.
Technical view
The flaw is an exploitable buffer overflow in the DDNS client used by Foscam C1 cameras running application firmware 2.52.2.43 with the listed system and plug-in versions. CVSS 3.0 is 8.1. Exploitation requires network positioning capable of intercepting HTTP traffic and a rogue HTTP server response path.
Likely exposure
Exposure is likely limited to Foscam C1 Indoor IP Camera C1 Series devices matching the listed firmware set, especially where DDNS is enabled and camera HTTP traffic can be intercepted.
Exploitation context
The source bundle says compromise is possible when DDNS is enabled and an attacker can intercept HTTP connections. KEV is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Evidence is strongest for the specific Foscam C1 firmware combination listed in the CVE bundle. The exploit condition is constrained by DDNS being enabled and attacker HTTP interception capability. No CWE, patched version, or active exploitation evidence is provided here.
Mitigation direction
- Identify Foscam C1 cameras and record firmware versions.
- Disable DDNS where it is not operationally required.
- Check Foscam guidance for fixed firmware or vendor-supported remediation.
- Segment cameras from sensitive networks and restrict management access.
- Avoid exposing camera traffic to untrusted or interceptable networks.
Validation and detection
- Inventory devices for Foscam C1 Indoor IP Camera C1 Series.
- Confirm system firmware, application firmware, and plug-in versions.
- Check whether DDNS is enabled on each device.
- Review network paths for HTTP interception risk.
- Verify vendor remediation status before marking resolved.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2017-2857 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
8.1HighVector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0360CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.