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

> Remote attackers can execute arbitrary code via crafted strings or filenames in the PocketNetNVRMediaClientAxCtrl control of 3S Pocketnet Tech VMS.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c6c5-c6cf-v8vh

## What is CVE-2014-9263?

CVE-2014-9263 is a medium-severity memory corruption vulnerability in n/a, published on 8 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in the PocketNetNVRMediaClientAxCtrl.NVRMediaViewer.1 control in 3S Pocketnet Tech VMS allow remote attackers to execute arbitrary code via a crafted string to the (1) StartRecord, (2) StartRecordEx, (3) StartScheduledRecord, (4) SetDisplayText, (5) GetONVIFDeviceInformation, (6) GetONVIFProfiles, or (7) GetONVIFStreamUri method or a crafted filename to the (8) SaveCurrentImage or (9) SaveCurrentImageEx method.

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

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

It affects 1 product.


Products: 3s Pocketnet Tech 3s Pocketnet Tech Video Management Software.

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

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

## Is CVE-2014-9263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9263 is a medium-severity memory corruption vulnerability in n/a, published on 8 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9263 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-9263/ (Markdown: https://insights.sbomify.com/CVE-2014-9263/index.md)
```

## Sources

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

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