{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32707 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32707 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32707 is a medium-severity vulnerability in nextcloud security-advisories, published on 12 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32707 and fix it if it is affected.\n\nWhat it is: CVE-2021-32707 is a medium-severity vulnerability in nextcloud security-advisories, published on 12 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32707 in the wild and no public exploit code.\n\nAffected product: nextcloud security-advisories. 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-32707/ (Markdown: https://insights.sbomify.com/CVE-2021-32707/index.md)","id":"CVE-2021-32707","markdown":"https://insights.sbomify.com/CVE-2021-32707/index.md","name":"CVE-2021-32707","record":{"aliases":["GHSA-xxp4-44xc-8crh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nextcloud Mail app","requires_auth":"low_privilege","summary":"Attackers can bypass image blocking in Nextcloud Mail via CSS background images, potentially revealing user read status.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mail","vendor":"nextcloud"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Nextcloud Mail is a mail app for Nextcloud. In versions prior to 1.9.6, the Nextcloud Mail application does not, by default, render images in emails to not leak the read state. The privacy filter failed to filter images with a `background-image` CSS attribute. Note that the images were still passed through the Nextcloud image proxy, and thus there was no IP leakage. The issue was patched in version 1.9.6 and 1.10.0. No workarounds are known to exist.","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":"Bypass of image blocking in Nextcloud Mail","id":"CVE-2021-32707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Time-of-check Time-of-use (TOCTOU) Race Condition in league/flysystem","id":"CVE-2021-32708"},"packages":[],"prev":{"headline":"(Authenticated) Remote Code Execution Possible in Web Interface 5.5","id":"CVE-2021-32706"},"products":["security-advisories"],"published":"2021-07-12","related":[{"cvss_score":8.8,"headline":"Missing permission check on email metadata retrieval","id":"CVE-2021-32652","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":8.3,"headline":"Unauthenticated SSRF in 3rd party module \"cerdic/csstidy\"","id":"CVE-2022-31132","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":8.2,"headline":"Nextcloud Mail auto configurator can be tricked into sending account information to wrong servers","id":"CVE-2024-52508","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":5,"headline":"Blind SSRF via server URL input in the Nextcloud Mail app","id":"CVE-2023-23943","kev_date_added":null,"published":"2023-02-06"},{"cvss_score":4.3,"headline":"Require strict cookies for image proxy requests in Nextcloud Mail","id":"CVE-2023-45660","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":4.1,"headline":"IDOR Vulnerability in Nextcloud Mail","id":"CVE-2023-25160","kev_date_added":null,"published":"2023-02-13"}],"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":["nextcloud"]},"summary":"Attackers can bypass image blocking in Nextcloud Mail via CSS background images, potentially revealing user read status.","url":"https://insights.sbomify.com/CVE-2021-32707/"}