# CVE-2014-1849: Weak cryptography in n/a

> Remote attackers can hijack IP cameras by exploiting predictable DynDNS credentials, requiring the DynDNS feature to be enabled.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rhvc-938p-pfqm

## What is CVE-2014-1849?

CVE-2014-1849 is a critical vulnerability in n/a, published on 14 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-255

## Which versions are affected by CVE-2014-1849?

It affects 1 product.


Products: Foscam Ip Camera Firmware.

## How do I fix CVE-2014-1849?

No fix has been published for CVE-2014-1849 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-1849 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-1849 exists.

Public exploit code:

- Foscam IP Camera - Predictable Credentials Security Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1849 and fix it if it is affected.

What it is: CVE-2014-1849 is a critical vulnerability in n/a, published on 14 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-1849 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-1849/ (Markdown: https://insights.sbomify.com/CVE-2014-1849/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-1849
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-1849
- OSV: https://osv.dev/vulnerability/CVE-2014-1849

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-1849/
Summaries are generated and may contain mistakes; the official description above is the record.