# CVE-2022-29729: Weak cryptography in n/a

> Weak default admin password generation allows unauthenticated attackers to access the webUI login page and take over the device.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xxq7-hjr2-f27f

## What is CVE-2022-29729?

CVE-2022-29729 is a high-severity vulnerability in n/a, published on 27 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Verizon 4G LTE Network Extender GA4.38 - V0.4.038.2131 utilizes a weak default admin password generation algorithm which generates passwords that are accessible to unauthenticated attackers via the webUI login page.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Verizon 4g Lte Network Extender Firmware.

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

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

## Is CVE-2022-29729 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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