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

> Remote attackers can crash the camera or execute arbitrary code via a buffer overflow in the RTSP handler.

- **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:** 3 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vpxj-5f34-wf7j

## What is CVE-2013-4977?

CVE-2013-4977 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 the RTSP Packet Handler in Hikvision DS-2CD7153-E IP camera with firmware 4.1.0 b130111 (Jan 2013), and possibly other devices, allows remote attackers to cause a denial of service (device crash and reboot) and possibly execute arbitrary code via a long string in the Range header field in an RTSP transaction.

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

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

It affects 2 products.


Products: Hikvision Ds-2cd7153-E, Hikvision Ds-2cd7153-E Firmware.

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

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

## Is CVE-2013-4977 being exploited?

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

Public exploit code:

- Hikvision IP Cameras 4.1.0 b130111 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4977 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-4977 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-4977/ (Markdown: https://insights.sbomify.com/CVE-2013-4977/index.md)
```

## Sources

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

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