{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41055 exists.","fix":"No fix has been published for CVE-2023-41055 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41055 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-41055 and fix it if it is affected.\n\nWhat it is: CVE-2023-41055 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-41055 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-41055/ (Markdown: https://insights.sbomify.com/CVE-2023-41055/index.md)","id":"CVE-2023-41055","markdown":"https://insights.sbomify.com/CVE-2023-41055/index.md","name":"CVE-2023-41055","record":{"aliases":["GHSA-xfj6-4vp9-8rgc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreY meta search engine","requires_auth":"none","summary":"Remote attackers can trigger SSRF via the wikipedia_language cookie, causing Denial of Service or data exfiltration in LibreY.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"librey","vendor":"ahwx"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 `engines/google/text.php` and `engines/duckduckgo/text.php` files in versions before commit be59098abd119cda70b15bf3faac596dfd39a744. This vulnerability allows remote attackers to request the server to send HTTP GET requests to arbitrary targets and conduct Denial-of-Service (DoS) attacks via the `wikipedia_language` cookie. Remote attackers can request the server to download large files to reduce the performance of the server or even deny access from legitimate users. This issue has been patched in https://github.com/Ahwxorg/LibreY/pull/9. 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 via wikipedia_language cookie","id":"CVE-2023-41055","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Redis vulnerable to integer overflow in certain payloads","id":"CVE-2023-41056"},"packages":[],"prev":{"headline":"LibreY Server-Side Request Forgery (SSRF) vulnerability in image_proxy.php","id":"CVE-2023-41054"},"products":["LibreY"],"published":"2023-09-04","related":[{"cvss_score":8.2,"headline":"LibreY Server-Side Request Forgery (SSRF) vulnerability in image_proxy.php","id":"CVE-2023-41054","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 trigger SSRF via the wikipedia_language cookie, causing Denial of Service or data exfiltration in LibreY.","url":"https://insights.sbomify.com/CVE-2023-41055/"}