{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-42465 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-42465 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-42465 is a critical missing authorization vulnerability in upKeeper Manager, published on 16 Aug 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-42465 and fix it if it is affected.\n\nWhat it is: CVE-2024-42465 is a critical missing authorization vulnerability in upKeeper Manager, published on 16 Aug 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-42465 in the wild and no public exploit code.\n\nAffected product: upKeeper Manager. 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-42465/ (Markdown: https://insights.sbomify.com/CVE-2024-42465/index.md)","id":"CVE-2024-42465","markdown":"https://insights.sbomify.com/CVE-2024-42465/index.md","name":"CVE-2024-42465","record":{"aliases":["GHSA-52g6-2pfv-hfcq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"upKeeper Manager","requires_auth":"low_privilege","summary":"Attackers can bypass two-factor authentication via brute-force attacks due to missing rate limiting, potentially taking over user accounts.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"upKeeper","cpe":[{"product":"upkeeper_manager","vendor":"upkeeper"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Improper Restriction of Excessive Authentication Attempts vulnerability in upKeeper Solutions product upKeeper Manager allows Authentication Abuse.This issue affects upKeeper Manager: through 5.1.9.","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":"Lack of resources and rate limiting - two factor authentication","id":"CVE-2024-42465","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Lack of resources and rate limiting - login","id":"CVE-2024-42466"},"packages":[],"prev":{"headline":"Leak of user information","id":"CVE-2024-42464"},"products":["upKeeper Manager"],"published":"2024-08-16","related":[{"cvss_score":10,"headline":"Bypass multifactor authentication","id":"CVE-2024-42462","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":9.5,"headline":"Lack of resources and rate limiting - login","id":"CVE-2024-42466","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":8.8,"headline":"Information disclosure in upKeeper Manager","id":"CVE-2025-8663","kev_date_added":null,"published":"2025-09-03"},{"cvss_score":8.6,"headline":"Leak of organizations messages","id":"CVE-2024-42463","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":7.6,"headline":"Leak of user information","id":"CVE-2024-42464","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":7.3,"headline":"Information disclosure in upKeeper Manager","id":"CVE-2025-11446","kev_date_added":null,"published":"2025-11-19"}],"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-16","vendors":["upKeeper Solutions"]},"summary":"Attackers can bypass two-factor authentication via brute-force attacks due to missing rate limiting, potentially taking over user accounts.","url":"https://insights.sbomify.com/CVE-2024-42465/"}