# CVE-2024-50634: Auth bypass in n/a

> Attackers can escalate privileges and bypass authentication in Watcharr by exploiting weak JWT token generation.
 

- **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:** 8 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-mmv8-59h2-5hqj

## What is CVE-2024-50634?

CVE-2024-50634 is a high-severity authentication bypass vulnerability in n/a, published on 8 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in a weak JWT token in Watcharr v1.43.0 and below allows attackers to perform privilege escalation using a crafted JWT token. This vulnerability is not limited to privilege escalation but also affects all functions that require authentication.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2024-50634?

It affects 1 product.


Products: Sbond Watcharr.

## How do I fix CVE-2024-50634?

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

## Is CVE-2024-50634 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50634 exists.

## Other vulnerabilities in n/a

- [CVE-2024-48827](https://insights.sbomify.com/CVE-2024-48827/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50634 and fix it if it is affected.

What it is: CVE-2024-50634 is a high-severity authentication bypass vulnerability in n/a, published on 8 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50634 exists.

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-2024-50634/ (Markdown: https://insights.sbomify.com/CVE-2024-50634/index.md)
```

## Sources

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

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