# CVE-2019-13379: Auth bypass in n/a

> An attacker can reset the device to factory defaults via a web interface command and log in with default credentials to gain administrator access.

- **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:** 7 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xg6v-xh9g-65cv

## What is CVE-2019-13379?

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

### Official description

On AVTECH Room Alert 3E devices before 2.2.5, an attacker with access to the device's web interface may escalate privileges from an unauthenticated user to administrator by performing a cmd.cgi?action=ResetDefaults&src=RA reset and using the default credentials to get in.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Avtech Room Alert 3e Firmware.

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

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

## Is CVE-2019-13379 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13379 is a high-severity authentication bypass vulnerability in n/a, published on 7 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-13379 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-13379/ (Markdown: https://insights.sbomify.com/CVE-2019-13379/index.md)
```

## Sources

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

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