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

> Attackers with administrative privileges can recover cleartext backup encryption passwords due to reversible storage mechanisms.

- **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:** 9 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gwgv-9chf-4hqg

## What is CVE-2022-36617?

CVE-2022-36617 is a medium-severity vulnerability in n/a, published on 9 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Arq Backup 7.19.5.0 and below stores backup encryption passwords using reversible encryption. This issue allows attackers with administrative privileges to recover cleartext passwords.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Haystacksoftware Arq Backup.

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

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

## Is CVE-2022-36617 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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