# CVE-2014-1201: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in the Lorex Edge camera ActiveX control via a long HTTP_PORT parameter, potentially causing a crash or executing arbitrary code.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wx86-c74j-r585

## What is CVE-2014-1201?

CVE-2014-1201 is a critical memory corruption vulnerability in n/a, published on 15 Jan 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the INetViewX ActiveX control in the Lorex Edge LH310 and Edge+ LH320 series with firmware 7-35-28-1B26E, Edge2 LH330 series with firmware 11.17.38-33_1D97A, and Edge3 LH340 series with firmware 11.19.85_1FE3A allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in the HTTP_PORT parameter.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 8 products.


Products: Lorex Technology Edge2 Lh330 Firmware, Lorex Technology Edge3 Lh340 Firmware, Lorex Technology Edge\+ Lh320 Firmware, Lorex Technology Edge Lh310 Firmware, Lorextechnology Edge, Lorextechnology Edge2, Lorextechnology Edge3, Lorextechnology Edge\+.

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

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

## Is CVE-2014-1201 being exploited?

There is no known exploitation of CVE-2014-1201 in the wild and no public exploit code.

Public exploit code:

- Lorex LH300 Series - ActiveX Buffer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-1201 is a critical memory corruption vulnerability in n/a, published on 15 Jan 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-1201 in the wild and no public exploit code.

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-1201/ (Markdown: https://insights.sbomify.com/CVE-2014-1201/index.md)
```

## Sources

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

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