{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-37619 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-37619 is a medium-severity memory corruption vulnerability in Exiv2 Exiv2, published on 9 Aug 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-37619 and fix it if it is affected.\n\nWhat it is: CVE-2021-37619 is a medium-severity memory corruption vulnerability in Exiv2 Exiv2, published on 9 Aug 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-37619 in the wild and no public exploit code.\n\nAffected product: Exiv2 Exiv2. 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-37619/ (Markdown: https://insights.sbomify.com/CVE-2021-37619/index.md)","id":"CVE-2021-37619","markdown":"https://insights.sbomify.com/CVE-2021-37619/index.md","name":"CVE-2021-37619","record":{"aliases":["AZL-7221","CLEANSTART-2024-RJ67281","DEBIAN-CVE-2021-37619","GHSA-mxw9-qx4c-6m8v","JLSEC-2026-1309","UBUNTU-CVE-2021-37619"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Image metadata library","requires_auth":"none","summary":"An out-of-bounds read in Exiv2 allows attackers to cause a denial of service by crashing the application when writing metadata to a crafted image file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"exiv2","vendor":"exiv2"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. An out-of-bounds read was found in Exiv2 versions v0.27.4 and earlier. The out-of-bounds read is triggered when Exiv2 is used to write metadata into a crafted image file. An attacker could potentially exploit the vulnerability to cause a denial of service by crashing Exiv2, if they can trick the victim into running Exiv2 on a crafted image file. Note that this bug is only triggered when writing the metadata, which is a less frequently used Exiv2 operation than reading the metadata. For example, to trigger the bug in the Exiv2 command-line application, you need to add an extra command-line argument such as insert. The bug is fixed in version v0.27.5.","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":"Out-of-bounds read in Exiv2::Jp2Image::encodeJp2Header","id":"CVE-2021-37619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"exiv2:exiv2","products":["exiv2:exiv2","fedoraproject:fedora"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":5,"next":{"headline":"Out-of-bounds read in XmpTextValue::read()","id":"CVE-2021-37620"},"packages":[],"prev":{"headline":"Out-of-bounds read in Exiv2::Jp2Image::printStructure","id":"CVE-2021-37618"},"products":["exiv2"],"published":"2021-08-09","related":[{"cvss_score":8.8,"headline":"Out-of-bounds write in exiv2","id":"CVE-2023-44398","kev_date_added":null,"published":"2023-11-06"},{"cvss_score":8.8,"headline":"Denial of service in n/a","id":"CVE-2019-9143","kev_date_added":null,"published":"2019-02-25"},{"cvss_score":8.8,"headline":"Denial of service in n/a","id":"CVE-2019-9144","kev_date_added":null,"published":"2019-02-25"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14046","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-12955","kev_date_added":null,"published":"2017-08-18"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2018-14338","kev_date_added":null,"published":"2018-07-17"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-9305","kev_date_added":null,"published":"2018-04-04"}],"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":["Exiv2"]},"summary":"An out-of-bounds read in Exiv2 allows attackers to cause a denial of service by crashing the application when writing metadata to a crafted image file.","url":"https://insights.sbomify.com/CVE-2021-37619/"}