{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55008 exists.","fix":"No fix has been published for CVE-2024-55008 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-55008 is a high-severity denial of service vulnerability in n/a, published on 7 Jan 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-55008 and fix it if it is affected.\n\nWhat it is: CVE-2024-55008 is a high-severity denial of service vulnerability in n/a, published on 7 Jan 2025. 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-2024-55008 exists.\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-55008/ (Markdown: https://insights.sbomify.com/CVE-2024-55008/index.md)","id":"CVE-2024-55008","markdown":"https://insights.sbomify.com/CVE-2024-55008/index.md","name":"CVE-2024-55008","record":{"aliases":["GHSA-jxq8-vf97-xqr3"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JATOS survey platform","requires_auth":"none","summary":"Attackers can lock legitimate users out of JATOS accounts by triggering the account-level lockout mechanism with repeated failed login attempts.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jatos","vendor":"jatos"}],"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":"JATOS 3.9.4 contains a denial-of-service (DoS) vulnerability in the authentication system, where an attacker can prevent legitimate users from accessing their accounts by repeatedly sending multiple failed login attempts. Specifically, by submitting 3 incorrect login attempts every minute, the attacker can trigger the account lockout mechanism on the account level, effectively locking the user out indefinitely. Since the lockout is applied to the user account and not based on the IP address, any attacker can trigger the lockout on any user account, regardless of their privileges.","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":"Denial of service in n/a","id":"CVE-2024-55008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-55009"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-55000"},"products":["n/a"],"published":"2025-01-07","related":[{"cvss_score":8.4,"headline":"Cross-site scripting in n/a","id":"CVE-2024-51379","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":8.4,"headline":"Cross-site scripting in n/a","id":"CVE-2024-51380","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":8.4,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-51381","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":8.4,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-51382","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":5.5,"headline":"JATOS ZIP ZipUtil.java ZipUtil path traversal","id":"CVE-2022-4878","kev_date_added":null,"published":"2023-01-06"}],"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":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can lock legitimate users out of JATOS accounts by triggering the account-level lockout mechanism with repeated failed login attempts.","url":"https://insights.sbomify.com/CVE-2024-55008/"}