# CVE-2023-49801: Lif Auth Server vulnerable to uncontrolled data in path expression


- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-3v77-pvqq-qg3f

## What is CVE-2023-49801?

CVE-2023-49801 is a medium-severity vulnerability in Lif-Platforms Lif-Auth-Server, published on 12 Jan 2024. 

### Official description

Lif Auth Server is a server for validating logins, managing information, and account recovery for Lif Accounts. The issue relates to the `get_pfp` and `get_banner` routes on Auth Server. The issue is that there is no check to ensure that the file that Auth Server is receiving through these URLs is correct. This could allow an attacker access to files they shouldn't have access to. This issue has been patched in version 1.4.0.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Lifplatforms Lif Auth Server.

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

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

## Is CVE-2023-49801 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49801 is a medium-severity vulnerability in Lif-Platforms Lif-Auth-Server, published on 12 Jan 2024. 
Exploitation: There is no known exploitation of CVE-2023-49801 in the wild and no public exploit code.

Affected product: Lif-Platforms Lif-Auth-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-49801/ (Markdown: https://insights.sbomify.com/CVE-2023-49801/index.md)
```

## Sources

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

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