# CVE-2023-49091: Jwttoken in Cosmos server never expires after password changed and logging out

> Attackers can retain unauthorized access to Cosmos Server using JWT tokens that remain valid after user logout or password change.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Nov 2023
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-hpvm-x7m8-3c6x

## What is CVE-2023-49091?

CVE-2023-49091 is a high-severity authentication bypass vulnerability in azukaar Cosmos-Server, published on 29 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cosmos provides users the ability self-host a home server by acting as a secure gateway to your application, as well as a server manager. Cosmos-server is vulnerable due to to the authorization header used for user login remaining valid and not expiring after log out. This vulnerability allows an attacker to use the token to gain unauthorized access to the application/system even after the user has logged out. This issue has been patched in version 0.13.1.

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

## Which versions are affected by CVE-2023-49091?

It affects 1 product.


Products: Cosmos-Cloud Cosmos Server.

## How do I fix CVE-2023-49091?

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

## Is CVE-2023-49091 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49091 and fix it if it is affected.

What it is: CVE-2023-49091 is a high-severity authentication bypass vulnerability in azukaar Cosmos-Server, published on 29 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49091 exists.

Affected product: azukaar Cosmos-Server. 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-2023-49091/ (Markdown: https://insights.sbomify.com/CVE-2023-49091/index.md)
```

## Sources

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

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