{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41054 exists.","fix":"No fix has been published for CVE-2023-41054 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41054 is a high-severity server-side request forgery vulnerability in Ahwxorg LibreY, published on 4 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41054 and fix it if it is affected.\n\nWhat it is: CVE-2023-41054 is a high-severity server-side request forgery vulnerability in Ahwxorg LibreY, published on 4 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41054 exists.\n\nAffected product: Ahwxorg LibreY. 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-41054/ (Markdown: https://insights.sbomify.com/CVE-2023-41054/index.md)","id":"CVE-2023-41054","markdown":"https://insights.sbomify.com/CVE-2023-41054/index.md","name":"CVE-2023-41054","record":{"aliases":["GHSA-p4f9-h8x8-mpwf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreY meta search engine","requires_auth":"none","summary":"Remote attackers can exploit LibreY to send arbitrary HTTP requests, enabling internal network data retrieval and denial-of-service attacks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"librey","vendor":"ahwx"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"LibreY is a fork of LibreX, a framework-less and javascript-free privacy respecting meta search engine. LibreY is subject to a Server-Side Request Forgery (SSRF) vulnerability in the `image_proxy.php` file of LibreY before commit 8f9b9803f231e2954e5b49987a532d28fe50a627. This vulnerability allows remote attackers to use the server as a proxy to send HTTP GET requests to arbitrary targets and retrieve information in the internal network or conduct Denial-of-Service (DoS) attacks via the `url` parameter. Remote attackers can use the server as a proxy to send HTTP GET requests and retrieve information in the internal network. Remote attackers can also request the server to download large files or chain requests among multiple instances to reduce the performance of the server or even deny access from legitimate users. This issue has been addressed in https://github.com/Ahwxorg/LibreY/pull/31. LibreY hosters are advised to use the latest commit. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LibreY Server-Side Request Forgery (SSRF) vulnerability in image_proxy.php","id":"CVE-2023-41054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"LibreY Server-Side Request Forgery (SSRF) vulnerability via wikipedia_language cookie","id":"CVE-2023-41055"},"packages":[],"prev":{"headline":"Redis SORT_RO may bypass ACL configuration","id":"CVE-2023-41053"},"products":["LibreY"],"published":"2023-09-04","related":[{"cvss_score":7.5,"headline":"LibreY Server-Side Request Forgery (SSRF) vulnerability via wikipedia_language cookie","id":"CVE-2023-41055","kev_date_added":null,"published":"2023-09-04"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-30","vendors":["Ahwxorg"]},"summary":"Remote attackers can exploit LibreY to send arbitrary HTTP requests, enabling internal network data retrieval and denial-of-service attacks.","url":"https://insights.sbomify.com/CVE-2023-41054/"}