# CVE-2013-4976: Hardcoded credentials in n/a

> Attackers can bypass security controls and gain unauthorized access to Hikvision IP cameras using hardcoded credentials.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3rhg-f794-8r8h

## What is CVE-2013-4976?

CVE-2013-4976 is a critical vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hikvision DS-2CD7153-E IP Camera has security bypass via hardcoded credentials

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Hikvision Ds-2cd7153-E Firmware.

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

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

## Is CVE-2013-4976 being exploited?

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

Public exploit code:

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

## Other vulnerabilities in n/a

- [CVE-2013-4975](https://insights.sbomify.com/CVE-2013-4975/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4976 is a critical vulnerability in n/a, published on 27 Dec 2019. 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-4976 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-4976/ (Markdown: https://insights.sbomify.com/CVE-2013-4976/index.md)
```

## Sources

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

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