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

> Remote attackers can gain privileges on CRU Ditto Forensic FieldStation devices using default hardcoded credentials.

- **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:** 7 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3r65-2rvr-4m87

## What is CVE-2013-6884?

CVE-2013-6884 is a critical vulnerability in n/a, published on 7 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The write-blocker in CRU Ditto Forensic FieldStation with firmware before 2013Oct15a has a default "ditto" username and password, which allows remote attackers to gain privileges.

Weakness: CWE-255

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

It affects 2 products.


Products: Cru-Inc Ditto Forensic Fieldstation, Cru-Inc Ditto Forensic Fieldstation Firmware.

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

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

## Is CVE-2013-6884 being exploited?

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

Public exploit code:

- Ditto Forensic FieldStation 2013Oct15a - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-6881](https://insights.sbomify.com/CVE-2013-6881/): Command injection in n/a (critical 10.0)
- [CVE-2013-6883](https://insights.sbomify.com/CVE-2013-6883/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-6882](https://insights.sbomify.com/CVE-2013-6882/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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