# CVE-2013-4981: Memory corruption in n/a

> Remote attackers can crash the device or execute arbitrary code via a buffer overflow in the SMTP configuration parameter.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 3 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rwf7-5g3r-wfvw

## What is CVE-2013-4981?

CVE-2013-4981 is a critical memory corruption vulnerability in n/a, published on 3 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in cgi-bin/user/Config.cgi in AVTECH AVN801 DVR with firmware 1017-1003-1009-1003 and earlier, and possibly other devices, allows remote attackers to cause a denial of service (device crash) and possibly execute arbitrary code via a long string in the Network.SMTP.Receivers parameter.

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

## Which versions are affected by CVE-2013-4981?

It affects 2 products.


Products: Avtech Avn801 Dvr, Avtech Avn801 Dvr Firmware.

## How do I fix CVE-2013-4981?

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

## Is CVE-2013-4981 being exploited?

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

Public exploit code:

- AVTECH DVR Firmware 1017-1003-1009-1003 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-4980](https://insights.sbomify.com/CVE-2013-4980/): Memory corruption in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4981 and fix it if it is affected.

What it is: CVE-2013-4981 is a critical memory corruption vulnerability in n/a, published on 3 Mar 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-2013-4981 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-2013-4981/ (Markdown: https://insights.sbomify.com/CVE-2013-4981/index.md)
```

## Sources

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

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