{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49801 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49801 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49801 is a medium-severity vulnerability in Lif-Platforms Lif-Auth-Server, published on 12 Jan 2024."},"fix_prompt":"Check this codebase for CVE-2023-49801 and fix it if it is affected.\n\nWhat it is: CVE-2023-49801 is a medium-severity vulnerability in Lif-Platforms Lif-Auth-Server, published on 12 Jan 2024. \nExploitation: There is no known exploitation of CVE-2023-49801 in the wild and no public exploit code.\n\nAffected product: Lif-Platforms Lif-Auth-Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-49801/ (Markdown: https://insights.sbomify.com/CVE-2023-49801/index.md)","id":"CVE-2023-49801","markdown":"https://insights.sbomify.com/CVE-2023-49801/index.md","name":"CVE-2023-49801","record":{"aliases":["GHSA-3v77-pvqq-qg3f"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"lif_auth_server","vendor":"lifplatforms"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-23","name":"Relative Path Traversal"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Lif Auth Server vulnerable to uncontrolled data in path expression","id":"CVE-2023-49801","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"MantisBT LinkedCustomFields Cross-site Scripting vulnerability","id":"CVE-2023-49802"},"packages":[],"prev":{"headline":"Denial of service by abusing `fetchOptions.retry` in nuxt-api-party","id":"CVE-2023-49800"},"products":["Lif-Auth-Server"],"published":"2024-01-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-14","vendors":["Lif-Platforms"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2023-49801/"}