LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34624: Mealie1.0.0beta3 does not terminate download tokens after a user logs out, allowing attackers to perform a...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-34624 describes a session-handling weakness in Mealie 1.0.0beta3. Download tokens reportedly remain valid after a user logs out. If an attacker can intercept or obtain such a token, they may be able to reuse it to access downloads. No active exploitation is reported in the provided sources.

Executive priority

Treat this as a targeted data-access risk, not a confirmed emergency. Prioritize if Mealie 1.0.0beta3 is internet-facing, handles sensitive recipes or user data, or operates on untrusted networks.

Technical view

The CVE states that Mealie 1.0.0beta3 does not terminate download tokens on logout, enabling a man-in-the-middle attacker to use a crafted GET request. The public metadata does not provide CVSS, CWE, detailed affected CPEs, or a named patch version.

Likely exposure

Exposure appears limited to deployments of Mealie 1.0.0beta3, especially where download links or tokens may traverse untrusted networks or be logged, proxied, or intercepted. The CVE affected-product fields are incomplete, so confirm against installed application version and vendor advisories.

Exploitation context

The weakness requires access to a still-valid download token, such as through interception or leakage. The provided sources do not indicate public exploitation, mass scanning, or CISA KEV listing.

Researcher notes

Evidence is sparse. The CVE record names Mealie 1.0.0beta3, but structured affected-product data is listed as n/a and no CVSS is present. Do not assume impact beyond download-token reuse without confirming application behavior and vendor history.

Mitigation direction

  • Identify whether any Mealie 1.0.0beta3 instances are deployed.
  • Check Mealie project guidance for fixed versions or configuration recommendations.
  • Upgrade or retire affected beta deployments if vendor guidance supports it.
  • Ensure TLS is enforced for all Mealie access paths.
  • Review proxies and logs for accidental token exposure.

Validation and detection

  • Confirm the running Mealie version from trusted asset records.
  • Test in staging whether download tokens expire after logout.
  • Review access logs for downloads occurring after user logout events.
  • Check whether download URLs or tokens appear in proxy, browser, or application logs.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-34624 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.