# CVE-2022-34624: Security feature bypass in n/a

> Attackers can intercept download tokens via man-in-the-middle attacks because tokens remain valid after logout, exposing user data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 19 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vc8q-vv59-f54c

## What is CVE-2022-34624?

CVE-2022-34624 is a medium-severity vulnerability in n/a, published on 19 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mealie1.0.0beta3 does not terminate download tokens after a user logs out, allowing attackers to perform a man-in-the-middle attack via a crafted GET request.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Mealie Mealie.

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

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

## Is CVE-2022-34624 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34615](https://insights.sbomify.com/CVE-2022-34615/): Weak cryptography in n/a (critical 9.8)
- [CVE-2025-56795](https://insights.sbomify.com/CVE-2025-56795/): Cross-site scripting in n/a (critical 9.0)
- [CVE-2024-55073](https://insights.sbomify.com/CVE-2024-55073/): Missing authorization in n/a (high 7.6)
- [CVE-2024-31992](https://insights.sbomify.com/CVE-2024-31992/): Mealie contains a DoS vulnerability in recipe importer (medium 6.5)
- [CVE-2024-31994](https://insights.sbomify.com/CVE-2024-31994/): Mealie vulnerable to a DoS in recipe image importer (GHSL-2023-228) (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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