{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-39212 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-39212 is a medium-severity vulnerability in Imagemagick Imagemagick, published on 13 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-39212 and fix it if it is affected.\n\nWhat it is: CVE-2021-39212 is a medium-severity vulnerability in Imagemagick Imagemagick, published on 13 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-39212 in the wild and no public exploit code.\n\nAffected product: Imagemagick Imagemagick. 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-39212/ (Markdown: https://insights.sbomify.com/CVE-2021-39212/index.md)","id":"CVE-2021-39212","markdown":"https://insights.sbomify.com/CVE-2021-39212/index.md","name":"CVE-2021-39212","record":{"aliases":["DEBIAN-CVE-2021-39212","GHSA-qvhr-jj4p-j2qr","JLSEC-2026-890","UBUNTU-CVE-2021-39212"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"ImageMagick library","requires_auth":"low_privilege","summary":"Attackers can bypass security policies to read or write Postscript files if module-based restrictions are used instead of coder-based ones.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"imagemagick","vendor":"imagemagick"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"},{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. In affected versions and in certain cases, Postscript files could be read and written when specifically excluded by a `module` policy in `policy.xml`. ex. \u003cpolicy domain=\"module\" rights=\"none\" pattern=\"PS\" /\u003e. The issue has been resolved in ImageMagick 7.1.0-7 and in 6.9.12-22. Fortunately, in the wild, few users utilize the `module` policy and instead use the `coder` policy that is also our workaround recommendation: \u003cpolicy domain=\"coder\" rights=\"none\" pattern=\"{PS,EPI,EPS,EPSF,EPSI}\" /\u003e.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Issue when Configuring the ImageMagick Security Policy","id":"CVE-2021-39212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"imagemagick:imagemagick","products":["imagemagick:imagemagick"],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"IP restriction on GLPI API Bypass with custom header injection","id":"CVE-2021-39213"},"packages":[],"prev":{"headline":"Disclosure of GLPI and server information in telemetry endpoint","id":"CVE-2021-39211"},"products":["ImageMagick"],"published":"2021-09-13","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2019-19952","kev_date_added":null,"published":"2019-12-24"},{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2018-16328","kev_date_added":null,"published":"2018-09-01"},{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2018-16329","kev_date_added":null,"published":"2018-09-01"},{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2017-18210","kev_date_added":null,"published":"2018-03-01"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2017-14138","kev_date_added":null,"published":"2017-09-04"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2014-9826","kev_date_added":null,"published":"2017-03-30"},{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2016-10144","kev_date_added":null,"published":"2017-03-24"}],"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-04","vendors":["ImageMagick"]},"summary":"Attackers can bypass security policies to read or write Postscript files if module-based restrictions are used instead of coder-based ones.","url":"https://insights.sbomify.com/CVE-2021-39212/"}