{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-29623 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-29623 is a low-severity vulnerability in Exiv2 Exiv2, published on 13 May 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-29623 and fix it if it is affected.\n\nWhat it is: CVE-2021-29623 is a low-severity vulnerability in Exiv2 Exiv2, published on 13 May 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-29623 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-29623/ (Markdown: https://insights.sbomify.com/CVE-2021-29623/index.md)","id":"CVE-2021-29623","markdown":"https://insights.sbomify.com/CVE-2021-29623/index.md","name":"CVE-2021-29623","record":{"aliases":["AZL-7212","CLEANSTART-2024-RH47389","DEBIAN-CVE-2021-29623","GHSA-6253-qjwm-3q4v","UBUNTU-CVE-2021-29623","openSUSE-SU-2024:12063-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Image metadata library","requires_auth":"none","summary":"An attacker can leak stack memory bytes by tricking a user into processing a crafted image file with the Exiv2 library.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"exiv2","vendor":"exiv2"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":3.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. A read of uninitialized memory was found in Exiv2 versions v0.27.3 and earlier. Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. The read of uninitialized memory is triggered when Exiv2 is used to read the metadata of a crafted image file. An attacker could potentially exploit the vulnerability to leak a few bytes of stack memory, if they can trick the victim into running Exiv2 on a crafted image file. The bug is fixed in version v0.27.4.","ecosystems":["openSUSE:Tumbleweed"],"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":"Uninitialized variable bug in Exiv2","id":"CVE-2021-29623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"exiv2:exiv2","products":["exiv2:exiv2","fedoraproject:fedora"],"type":"information_disclosure","year":"2021"},"n_packages":1,"n_references":7,"next":{"headline":"Lack of protection against cookie tossing attacks in fastify-csrf","id":"CVE-2021-29624"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.27.5-2.1"],"introduced":["0"],"last_affected":[],"package":"exiv2","purl":"pkg:rpm/opensuse/exiv2\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:12063-1"}],"prev":{"headline":"Arbitrary redirects under /new endpoint","id":"CVE-2021-29622"},"products":["exiv2"],"published":"2021-05-13","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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":["Exiv2"]},"summary":"An attacker can leak stack memory bytes by tricking a user into processing a crafted image file with the Exiv2 library.","url":"https://insights.sbomify.com/CVE-2021-29623/"}