CVE-2014-1849: n/a vulnerability

CVE-2014-1849: Foscam IP camera 11.37.2.49 and other versions, when using the Foscam DynDNS option, generates credentials...

Foscam IP camera 11.37.2.49 and other versions, when using the Foscam DynDNS option, generates credentials based on predictable camera subdomain names, which allows remote attackers to spoof or hijack arbitrary cameras and conduct other attacks by modifying arbitrary camera records in the Foscam DNS server.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 09:58 UTC (UTC+00:00)

Security readout for executives and security teams

This issue affects Foscam IP cameras using the Foscam DynDNS option. The service reportedly generated credentials from predictable camera subdomain names, allowing remote attackers to spoof or hijack camera DNS records. Business impact is loss of camera reachability or redirection through attacker-controlled records, but exact affected versions and fixes are not fully specified in the bundle. Exposure is most likely where legacy Foscam IP cameras use the Foscam DynDNS option. The source bundle does not identify all affected models, exact firmware ranges, or CPEs, so asset validation must focus on configuration and vendor confirmation. Prioritize if the organization still operates legacy Foscam cameras, especially internet-facing devices. The issue can undermine camera availability and trust in remote access records, and the age of the vulnerability increases concern for unsupported deployments. Mitigation focus: Inventory Foscam cameras and identify devices using Foscam DynDNS.; Disable Foscam DynDNS where it is not operationally required.; Check Foscam or reseller guidance for firmware updates or service changes..

Prepared: Jun 14, 2026, 14:16 UTC (UTC+00:00)

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.

cve · low confidence lookup

CVE-2014-1849 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: May 14, 2014, 00:00 UTC (UTC+00:00)

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

CVE List V5 sourceCVE List V5
https://github.com/artemharutyunyan/getmecamtool/blob/master/src/dnsmod.cCVE reference · x_refsource_MISC

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.