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

> Attackers with physical proximity can use default passwords to modify ZOLL defibrillator configurations, potentially causing denial of service and health risks.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6xq3-f7x8-hg44

## What is CVE-2013-7395?

CVE-2013-7395 is a medium-severity vulnerability in n/a, published on 12 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ZOLL Defibrillator / Monitor X Series has a default (1) supervisor password and (2) service password, which allows physically proximate attackers to modify device configuration and cause a denial of service (adverse human health effects).

Weakness: CWE-255

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

It affects 1 product.


Products: Zoll Monitor\/Defibrillator.

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

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

## Is CVE-2013-7395 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6756](https://insights.sbomify.com/CVE-2007-6756/): Hardcoded credentials in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7395 is a medium-severity vulnerability in n/a, published on 12 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7395 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-2013-7395/ (Markdown: https://insights.sbomify.com/CVE-2013-7395/index.md)
```

## Sources

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

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