{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6976 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-6976 is a medium-severity vulnerability in n/a, published on 26 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-6976 and fix it if it is affected.\n\nWhat it is: CVE-2019-6976 is a medium-severity vulnerability in n/a, published on 26 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-6976 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-6976/ (Markdown: https://insights.sbomify.com/CVE-2019-6976/index.md)","id":"CVE-2019-6976","markdown":"https://insights.sbomify.com/CVE-2019-6976/index.md","name":"CVE-2019-6976","record":{"aliases":["DEBIAN-CVE-2019-6976","GHSA-589q-f3gp-p53f","UBUNTU-CVE-2019-6976"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Image processing library","requires_auth":"none","summary":"Attackers can leak raw process memory contents by providing corrupted image data to the libvips library, potentially exposing sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libvips","vendor":"libvips"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"libvips before 8.7.4 generates output images from uninitialized memory locations when processing corrupted input image data because iofuncs/memory.c does not zero out allocated memory. This can result in leaking raw process memory contents through the output image.","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":"Information disclosure in n/a","id":"CVE-2019-6976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-6977"},"packages":[],"prev":{"headline":"Uncontrolled Memory Consumption in Django","id":"CVE-2019-6975"},"products":["n/a"],"published":"2019-01-26","related":[{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2019-17534","kev_date_added":null,"published":"2019-10-13"},{"cvss_score":7,"headline":"Possible integer overflow leading to potential heap-based buffer overflow","id":"CVE-2026-33327","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":7,"headline":"Possible heap-based buffer overflow when decoding TIFF image containing well-crafted tile","id":"CVE-2026-35591","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":6.8,"headline":"Possible integer overflow on 32-bit systems when reading GIF images","id":"CVE-2026-33328","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":6.8,"headline":"Possible out-of-bounds read leading to crash when decoding well-crafted EXIF metadata","id":"CVE-2026-35590","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2021-27847","kev_date_added":null,"published":"2021-07-15"}],"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":["n/a"]},"summary":"Attackers can leak raw process memory contents by providing corrupted image data to the libvips library, potentially exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2019-6976/"}