# CVE-2022-34907: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication to gain full administrative control over the FileWave platform.

- **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:** 25 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h25g-6x79-h5q2

## What is CVE-2022-34907?

CVE-2022-34907 is a critical authentication bypass vulnerability in n/a, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability exists in FileWave before 14.6.3 and 14.7.x before 14.7.2. Exploitation could allow an unauthenticated actor to gain access to the system with the highest authority possible and gain full control over the FileWave platform.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-34907?

It affects 1 product.


Products: Filewave Filewave.

## How do I fix CVE-2022-34907?

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

## Is CVE-2022-34907 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34906](https://insights.sbomify.com/CVE-2022-34906/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34907 and fix it if it is affected.

What it is: CVE-2022-34907 is a critical authentication bypass vulnerability in n/a, published on 25 Jul 2022. 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-2022-34907 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-2022-34907/ (Markdown: https://insights.sbomify.com/CVE-2022-34907/index.md)
```

## Sources

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

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