{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9149 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9149 is a high-severity vulnerability in n/a, published on 22 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-9149 and fix it if it is affected.\n\nWhat it is: CVE-2017-9149 is a high-severity vulnerability in n/a, published on 22 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-9149 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-2017-9149/ (Markdown: https://insights.sbomify.com/CVE-2017-9149/index.md)","id":"CVE-2017-9149","markdown":"https://insights.sbomify.com/CVE-2017-9149/index.md","name":"CVE-2017-9149","record":{"aliases":["GHSA-xg53-f74r-6v3r","UBUNTU-CVE-2017-9149"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Metadata Anonymisation Toolkit","requires_auth":"none","summary":"MAT fails to clean metadata when invoked via Nautilus, allowing attackers to read sensitive information from files intended to be sanitized.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"metadata_anonymisation_toolkit","vendor":"metadata_anonymisation_toolkit_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Metadata Anonymisation Toolkit (MAT) 0.6 and 0.6.1 silently fails to perform \"Clean metadata\" actions upon invocation from the Nautilus contextual menu, which allows context-dependent attackers to obtain sensitive information by reading a file for which cleaning had been attempted.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2017-9149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-9150"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2017-9148"},"products":["n/a"],"published":"2017-05-22","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"MAT fails to clean metadata when invoked via Nautilus, allowing attackers to read sensitive information from files intended to be sanitized.","url":"https://insights.sbomify.com/CVE-2017-9149/"}