{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-33857 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-33857 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-33857 is a critical server-side request forgery vulnerability in n/a, published on 7 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-33857 and fix it if it is affected.\n\nWhat it is: CVE-2024-33857 is a critical server-side request forgery vulnerability in n/a, published on 7 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-33857 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2024-33857/ (Markdown: https://insights.sbomify.com/CVE-2024-33857/index.md)","id":"CVE-2024-33857","markdown":"https://insights.sbomify.com/CVE-2024-33857/index.md","name":"CVE-2024-33857","record":{"aliases":["GHSA-52cx-m9j4-rq34"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Logpoint SIEM","requires_auth":"low_privilege","summary":"An attacker with low-level access can trigger Server Side Request Forgery in Logpoint due to lack of input validation on threat intelligence URLs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"siem","vendor":"logpoint"}],"cvss":{"score":9.6,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"An issue was discovered in Logpoint before 7.4.0. Due to a lack of input validation on URLs in threat intelligence, an attacker with low-level access to the system can trigger Server Side Request Forgery.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2024-33857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2024-33858"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2024-33856"},"products":["n/a"],"published":"2024-05-07","related":[{"cvss_score":8.5,"headline":"Cross-site scripting in SIEM","id":"CVE-2025-66359","kev_date_added":null,"published":"2025-11-27"},{"cvss_score":8.4,"headline":"Code injection in n/a","id":"CVE-2022-48684","kev_date_added":null,"published":"2024-04-27"},{"cvss_score":7.7,"headline":"Privilege escalation in n/a","id":"CVE-2022-48685","kev_date_added":null,"published":"2024-04-27"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2024-48950","kev_date_added":null,"published":"2024-11-07"},{"cvss_score":7.5,"headline":"Server-side request forgery in n/a","id":"CVE-2024-48951","kev_date_added":null,"published":"2024-11-07"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2024-48953","kev_date_added":null,"published":"2024-11-07"}],"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-08-02","vendors":["n/a"]},"summary":"An attacker with low-level access can trigger Server Side Request Forgery in Logpoint due to lack of input validation on threat intelligence URLs.","url":"https://insights.sbomify.com/CVE-2024-33857/"}