{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-3744 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3744 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3744 is a critical server-side request forgery vulnerability in SLiMS, published on 2 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-3744 and fix it if it is affected.\n\nWhat it is: CVE-2023-3744 is a critical server-side request forgery vulnerability in SLiMS, published on 2 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-3744 in the wild and no public exploit code.\n\nAffected product: SLiMS. 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-3744/ (Markdown: https://insights.sbomify.com/CVE-2023-3744/index.md)","id":"CVE-2023-3744","markdown":"https://insights.sbomify.com/CVE-2023-3744/index.md","name":"CVE-2023-3744","record":{"aliases":["GHSA-hjvr-v7mw-6f2j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SLiMS library system","requires_auth":"low_privilege","summary":"An authenticated attacker can exploit SSRF in SLiMS to access internal services or read files via the scrape_image.php endpoint.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"senayan_library_management_system","vendor":"slims"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Server-Side Request Forgery vulnerability in SLims version 9.6.0. This vulnerability could allow an authenticated attacker to send requests to internal services or upload the contents of relevant files via the \"scrape_image.php\" file in the imageURL parameter.","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":"Server-Side Request Forgery in SLiMS","id":"CVE-2023-3744","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Imagemagick: heap-buffer-overflow in pushcharpixel() in quantum-private.h","id":"CVE-2023-3745"},"packages":[],"prev":{"headline":"SQL injection vulnerability in LeoTheme's Ap Page Builder","id":"CVE-2023-3743"},"products":["SLiMS"],"published":"2023-10-02","related":[{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-38292","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2023-45996","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2023-40970","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2021-45791","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-12584","kev_date_added":null,"published":"2017-08-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-29850","kev_date_added":null,"published":"2023-04-14"}],"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":"total"},"state":"PUBLISHED","updated":"2024-09-20","vendors":["SLiMS"]},"summary":"An authenticated attacker can exploit SSRF in SLiMS to access internal services or read files via the scrape_image.php endpoint.","url":"https://insights.sbomify.com/CVE-2023-3744/"}