# CVE-2022-40756: Misconfiguration in n/a

> Attackers with file access can delete security files to reset the master password and gain unauthorized database access if folder permissions are misconfigured.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 30 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-vh67-wxr2-hr8p

## What is CVE-2022-40756?

CVE-2022-40756 is a high-severity vulnerability in n/a, published on 30 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

If folder security is misconfigured for Actian Zen PSQL BEFORE Patch Update 1 for Zen 15 SP1 (v15.11.005), Patch Update 4 for Zen 15 (v15.01.017), or Patch Update 5 for Zen 14 SP2 (v14.21.022), it can allow an attacker (with file read/write access) to remove specific security files in order to reset the master password and gain access to the database.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 2 products.


Products: Actian Psql, Actian Zen.

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

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

## Is CVE-2022-40756 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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