{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-57610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-57610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57610 is a high-severity denial of service vulnerability in n/a, published on 6 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-57610 and fix it if it is affected.\n\nWhat it is: CVE-2024-57610 is a high-severity denial of service vulnerability in n/a, published on 6 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-57610 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-57610/ (Markdown: https://insights.sbomify.com/CVE-2024-57610/index.md)","id":"CVE-2024-57610","markdown":"https://insights.sbomify.com/CVE-2024-57610/index.md","name":"CVE-2024-57610","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["denial_of_service","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Sylius e-commerce platform","requires_auth":"none","summary":"Remote attackers can perform unrestricted brute-force attacks on Sylius user accounts, risking account compromise and service disruption due to missing rate limiting.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sylius","vendor":"sylius"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"A rate limiting issue in Sylius v2.0.2 allows a remote attacker to perform unrestricted brute-force attacks on user accounts, significantly increasing the risk of account compromise and denial of service for legitimate users. The Supplier's position is that the Sylius core software is not intended to address brute-force attacks; instead, customers deploying a Sylius-based system are supposed to use \"firewalls, rate-limiting middleware, or authentication providers\" for that functionality.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-02-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-02-04T17:49:44Z","kind":"github_poc","ref":"https://github.com/H4ckM3-png/CVE-2024-57610","stars":0,"title":"Lack of Rate Limiting in Sylius v2.0.2"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2024-57610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2024-57611"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2024-57609"},"products":["n/a"],"published":"2025-02-06","related":[{"cvss_score":8.2,"headline":"Sylius has a Promotion Usage Limit Bypass via Race Condition","id":"CVE-2026-31824","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.1,"headline":"Sylius affected by IDOR in Cart and Checkout LiveComponents","id":"CVE-2026-31820","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.1,"headline":"Insufficient Session Expiration in Sylius","id":"CVE-2022-24743","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":6.9,"headline":"Sylius has an Open Redirect via Referer Header","id":"CVE-2026-31819","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.9,"headline":"Sylius is Missing Authorization in API v2 Add Item Endpoint","id":"CVE-2026-31821","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.4,"headline":"Sylius has potential Cross Site Scripting vulnerability via the \"Province\" field in the Checkout and Address Book","id":"CVE-2024-29376","kev_date_added":null,"published":"2024-04-22"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-07","vendors":["n/a"]},"summary":"Remote attackers can perform unrestricted brute-force attacks on Sylius user accounts, risking account compromise and service disruption due to missing rate limiting.","url":"https://insights.sbomify.com/CVE-2024-57610/"}