# CVE-2019-13402: Security feature bypass in n/a

> Incomplete factory reset on Dynacolor devices allows attackers to retain backdoors and system accounts, bypassing security controls.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7vjq-xg45-8px3

## What is CVE-2019-13402?

CVE-2019-13402 is a high-severity vulnerability in n/a, published on 8 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

/usr/sbin/default.sh and /usr/apache/htdocs/cgi-bin/admin/hardfactorydefault.cgi on Dynacolor FCM-MB40 v1.2.0.0 devices implement an incomplete factory-reset process. A backdoor can persist because neither system accounts nor the set of services is reset.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2019-13402?

It affects 1 product.


Products: Fortinet Fcm-Mb40 Firmware.

## How do I fix CVE-2019-13402?

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

## Is CVE-2019-13402 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13400](https://insights.sbomify.com/CVE-2019-13400/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-13401](https://insights.sbomify.com/CVE-2019-13401/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-13398](https://insights.sbomify.com/CVE-2019-13398/): Command injection in n/a (high 7.2)
- [CVE-2019-13399](https://insights.sbomify.com/CVE-2019-13399/): Hardcoded credentials in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13402 and fix it if it is affected.

What it is: CVE-2019-13402 is a high-severity vulnerability in n/a, published on 8 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13402 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-2019-13402/ (Markdown: https://insights.sbomify.com/CVE-2019-13402/index.md)
```

## Sources

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

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