{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3284 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3284 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3284 is a medium-severity vulnerability in M-Files New Web, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3284 and fix it if it is affected.\n\nWhat it is: CVE-2022-3284 is a medium-severity vulnerability in M-Files New Web, published on 6 Mar 2023. 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-3284 in the wild and no public exploit code.\n\nAffected product: M-Files New Web. 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-3284/ (Markdown: https://insights.sbomify.com/CVE-2022-3284/index.md)","id":"CVE-2022-3284","markdown":"https://insights.sbomify.com/CVE-2022-3284/index.md","name":"CVE-2022-3284","record":{"aliases":["GHSA-r92f-q253-q9wv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"M-Files New Web","requires_auth":"low_privilege","summary":"Attackers can obtain download keys via logs to access vault files in M-Files New Web.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"M-Files Corporation","cpe":[{"product":"m-files_server","vendor":"m-files"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Download key for a file in a vault was passed in an insecure way that could easily be logged in M-Files New Web in M-Files before 22.11.12011.0.\nThis issue affects M-Files New Web: before 22.11.12011.0.","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":"Insecure way of passing a download key","id":"CVE-2022-3284","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in GitLab","id":"CVE-2022-3285"},"packages":[],"prev":{"headline":"Denial of service in GitLab","id":"CVE-2022-3283"},"products":["M-Files New Web"],"published":"2023-03-06","related":[{"cvss_score":9.2,"headline":"Support for authentication bypass condition in M-Files LDAP authentication","id":"CVE-2024-10127","kev_date_added":null,"published":"2024-11-20"},{"cvss_score":8.4,"headline":"Path traversal in M-Files API","id":"CVE-2025-5964","kev_date_added":null,"published":"2025-06-15"},{"cvss_score":8.4,"headline":"Path traversal in M-Files API","id":"CVE-2024-6789","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":7.5,"headline":"Denial of service condition in M-Files Server","id":"CVE-2024-4056","kev_date_added":null,"published":"2024-04-26"},{"cvss_score":7.5,"headline":"Brute force vulnerability in M-Files user authentication","id":"CVE-2023-6912","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":7.5,"headline":"Denial of service condition in M-Files Server","id":"CVE-2023-3405","kev_date_added":null,"published":"2023-06-27"},{"cvss_score":7.5,"headline":"Uncontrolled Resource Consuption in M-Files Server","id":"CVE-2023-0383","kev_date_added":null,"published":"2023-04-20"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["M-Files"]},"summary":"Attackers can obtain download keys via logs to access vault files in M-Files New Web.","url":"https://insights.sbomify.com/CVE-2022-3284/"}