{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-24110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24110 is a medium-severity authentication bypass vulnerability in n/a, published on 14 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24110 and fix it if it is affected.\n\nWhat it is: CVE-2022-24110 is a medium-severity authentication bypass vulnerability in n/a, published on 14 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-24110 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-2022-24110/ (Markdown: https://insights.sbomify.com/CVE-2022-24110/index.md)","id":"CVE-2022-24110","markdown":"https://insights.sbomify.com/CVE-2022-24110/index.md","name":"CVE-2022-24110","record":{"aliases":["GHSA-48qq-gvpc-rg7v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Kiteworks MFT","requires_auth":"low_privilege","summary":"An unauthorized user can reset other users' passwords in Kiteworks MFT, leading to account takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"managed_file_transfer","vendor":"accellion"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Kiteworks MFT 7.5 may allow an unauthorized user to reset other users' passwords. This is fixed in version 7.6 and later.","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":"Auth bypass in n/a","id":"CVE-2022-24110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-24111"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2022-24109"},"products":["n/a"],"published":"2022-02-14","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"An unauthorized user can reset other users' passwords in Kiteworks MFT, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2022-24110/"}