# CVE-2022-29330: Missing authorization in n/a

> Attackers can access sensitive PBX credentials and voicemail files due to missing access controls in the backup system.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-rhr8-8xj2-r4pc

## What is CVE-2022-29330?

CVE-2022-29330 is a medium-severity missing authorization vulnerability in n/a, published on 24 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Missing access control in the backup system of Telesoft VitalPBX before 3.2.1 allows attackers to access the PJSIP and SIP extension credentials, cryptographic keys and voicemails files via unspecified vectors.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Vitalpbx Vitalpbx.

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

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

## Is CVE-2022-29330 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-0480](https://insights.sbomify.com/CVE-2023-0480/): Cross-site request forgery in VitalPBX (high 8.8)
- [CVE-2024-24386](https://insights.sbomify.com/CVE-2024-24386/): Code injection in n/a (high 7.2)
- [CVE-2023-0486](https://insights.sbomify.com/CVE-2023-0486/): Cross-site scripting in VitalPBX (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29330 is a medium-severity missing authorization vulnerability in n/a, published on 24 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29330 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-29330/ (Markdown: https://insights.sbomify.com/CVE-2022-29330/index.md)
```

## Sources

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

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