{"answers":{"affected":"2 open source packages ship an affected version, including snipe/snipe-it. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44381 exists.","fix":"No fix has been published for CVE-2022-44381 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44381 is a medium-severity vulnerability in Snipeitapp Snipe-It, published on 25 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-44381 and fix it if it is affected.\n\nWhat it is: CVE-2022-44381 is a medium-severity vulnerability in Snipeitapp Snipe-It, published on 25 Dec 2022. 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-2022-44381 exists.\n\nAffected packages and fixed versions:\n- snipe/snipe-it (Packagist): affected all versions up to 6.0.14; no fix listed\n- snipe/snipe-it (Packagist): affected all versions up to 6.0.14; no fix listed\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-44381/ (Markdown: https://insights.sbomify.com/CVE-2022-44381/index.md)","id":"CVE-2022-44381","markdown":"https://insights.sbomify.com/CVE-2022-44381/index.md","name":"CVE-2022-44381","record":{"aliases":["GHSA-qqv9-gqh5-7h99"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IT asset management","requires_auth":"none","summary":"Attackers can enumerate valid user accounts by analyzing response variations in password reset requests, exposing user existence information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"snipe-it","vendor":"snipeitapp"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Snipe-IT through 6.0.14 allows attackers to check whether a user account exists because of response variations in a /password/reset request.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Snipe-IT allows attackers to check whether a user account exists","id":"CVE-2022-44381","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"snipeitapp:snipe-it","products":["snipeitapp:snipe-it"],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2022-44384"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["6.0.14"],"package":"snipe/snipe-it","purl":null,"source":"GHSA-qqv9-gqh5-7h99"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["6.0.14"],"package":"snipe/snipe-it","purl":"pkg:composer/snipe/snipe-it","source":"GHSA-qqv9-gqh5-7h99"}],"prev":{"headline":"Snipe-IT vulnerable to Cross Site Scripting for View Assigned Assets","id":"CVE-2022-44380"},"products":["n/a"],"published":"2022-12-25","related":[{"cvss_score":9.9,"headline":"File upload in n/a","id":"CVE-2025-63601","kev_date_added":null,"published":"2025-11-05"},{"cvss_score":9.8,"headline":"Snipe-IT has insecure permissions in file uploads","id":"CVE-2026-37709","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":9.3,"headline":"Snipe-IT before 8.7.0 CSS Injection via Custom CSS","id":"CVE-2026-86738","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.2,"headline":"Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback","id":"CVE-2026-116199","kev_date_added":null,"published":"2026-10-25"},{"cvss_score":9.1,"headline":"Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it","id":"CVE-2022-1380","kev_date_added":null,"published":"2022-04-16"},{"cvss_score":9,"headline":"Stored Cross Site Scripting vulnerability in the checked_out_to parameter in snipe/snipe-it","id":"CVE-2022-1445","kev_date_added":null,"published":"2022-04-24"},{"cvss_score":8.8,"headline":"Snipe-IT - Host Header Injection","id":"CVE-2022-23064","kev_date_added":null,"published":"2022-05-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2025-04-15","vendors":["n/a"]},"summary":"Attackers can enumerate valid user accounts by analyzing response variations in password reset requests, exposing user existence information.","url":"https://insights.sbomify.com/CVE-2022-44381/"}