{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13960 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13960 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13960 is a medium-severity denial of service vulnerability in n/a, published on 18 Jul 2019. 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-2019-13960 and fix it if it is affected.\n\nWhat it is: CVE-2019-13960 is a medium-severity denial of service vulnerability in n/a, published on 18 Jul 2019. 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-2019-13960 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-13960/ (Markdown: https://insights.sbomify.com/CVE-2019-13960/index.md)","id":"CVE-2019-13960","markdown":"https://insights.sbomify.com/CVE-2019-13960/index.md","name":"CVE-2019-13960","record":{"aliases":["GHSA-mq63-35pw-h66r"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JPEG image library","requires_auth":"none","summary":"An attacker can cause denial of service by providing a malformed progressive JPEG image that triggers excessive memory consumption in libjpeg-turbo.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libjpeg-turbo","vendor":"libjpeg-turbo"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"In libjpeg-turbo 2.0.2, a large amount of memory can be used during processing of an invalid progressive JPEG image containing incorrect width and height values in the image header. NOTE: the vendor's expectation, for use cases in which this memory usage would be a denial of service, is that the application should interpret libjpeg warnings as fatal errors (aborting decompression) and/or set limits on resource consumption or image sizes","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":"Denial of service in n/a","id":"CVE-2019-13960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-13961"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-13959"},"products":["n/a"],"published":"2019-07-18","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-17541","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":8.8,"headline":"Integer overflow in n/a","id":"CVE-2018-20330","kev_date_added":null,"published":"2018-12-21"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2020-13790","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":6.5,"headline":"Memory corruption in libjpeg-turbo","id":"CVE-2023-2804","kev_date_added":null,"published":"2023-05-25"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2018-19664","kev_date_added":null,"published":"2018-11-29"},{"cvss_score":6.5,"headline":"Null dereference in n/a","id":"CVE-2017-15232","kev_date_added":null,"published":"2017-10-11"},{"cvss_score":5.5,"headline":"Null dereference in libjpeg-turbo","id":"CVE-2020-35538","kev_date_added":null,"published":"2022-08-31"}],"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-05","vendors":["n/a"]},"summary":"An attacker can cause denial of service by providing a malformed progressive JPEG image that triggers excessive memory consumption in libjpeg-turbo.","url":"https://insights.sbomify.com/CVE-2019-13960/"}