{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32750 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32750 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32750 is a medium-severity vulnerability in zlatinb muwire, published on 15 Jul 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-32750 and fix it if it is affected.\n\nWhat it is: CVE-2021-32750 is a medium-severity vulnerability in zlatinb muwire, published on 15 Jul 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-32750 in the wild and no public exploit code.\n\nAffected product: zlatinb muwire. 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-2021-32750/ (Markdown: https://insights.sbomify.com/CVE-2021-32750/index.md)","id":"CVE-2021-32750","markdown":"https://insights.sbomify.com/CVE-2021-32750/index.md","name":"CVE-2021-32750","record":{"aliases":["GHSA-68xh-9h7w-64qg"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MuWire desktop client","requires_auth":"low_privilege","summary":"An attacker can de-anonymize MuWire users by sending a message with an HTML image tag, causing the client to leak the user's IP address via clearnet.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"muwire","vendor":"muwire_project"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"MuWire is a file publishing and networking tool that protects the identity of its users by using I2P technology. Users of MuWire desktop client prior to version 0.8.8 can be de-anonymized by an attacker who knows their full ID. An attacker could send a message with a subject line containing a URL with an HTML image tag and the MuWire client would try to fetch that image via clearnet, thus exposing the IP address of the user. The problem is fixed in MuWire 0.8.8. As a workaround, users can disable messaging functionality to prevent other users from sending them malicious messages.","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":"De-anonymization via message","id":"CVE-2021-32750","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Arbitrary code execution via specially crafted environment variables","id":"CVE-2021-32751"},"packages":[],"prev":{"headline":"Possible RCE vulnerability in mailing action using mailutils (mail-whois)","id":"CVE-2021-32749"},"products":["muwire"],"published":"2021-07-15","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-08-03","vendors":["zlatinb"]},"summary":"An attacker can de-anonymize MuWire users by sending a message with an HTML image tag, causing the client to leak the user's IP address via clearnet.","url":"https://insights.sbomify.com/CVE-2021-32750/"}