{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28550 exists.","fix":"Apply the vendor's patch.","what":"CVE-2022-28550 is a critical memory corruption vulnerability in n/a, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-28550 and fix it if it is affected.\n\nWhat it is: CVE-2022-28550 is a critical memory corruption vulnerability in n/a, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28550 exists.\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-2022-28550/ (Markdown: https://insights.sbomify.com/CVE-2022-28550/index.md)","id":"CVE-2022-28550","markdown":"https://insights.sbomify.com/CVE-2022-28550/index.md","name":"CVE-2022-28550","record":{"aliases":["DEBIAN-CVE-2022-28550","GHSA-phqx-gjxc-wrp9","UBUNTU-CVE-2022-28550"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JPEG EXIF tool","requires_auth":"none","summary":"A stack buffer overflow in jhead allows attackers to execute arbitrary code or cause denial of service via crafted EXIF data.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jhead","vendor":"jhead_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Matthias-Wandel/jhead jhead 3.06 is vulnerable to Buffer Overflow via shellescape(), jhead.c, jhead. jhead copies strings to a stack buffer when it detects a \u0026i or \u0026o. However, jhead does not check the boundary of the stack buffer. As a result, there will be a stack buffer overflow problem when multiple `\u0026i` or `\u0026o` are given.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2022-28550","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2022-28552"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-28545"},"products":["n/a"],"published":"2023-06-13","related":[{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2025-44906","kev_date_added":null,"published":"2025-05-30"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28277","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28278","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.8,"headline":"Memory corruption in jhead","id":"CVE-2021-3496","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2018-16554","kev_date_added":null,"published":"2018-09-16"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2018-17088","kev_date_added":null,"published":"2018-09-16"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-03","vendors":["n/a"]},"summary":"A stack buffer overflow in jhead allows attackers to execute arbitrary code or cause denial of service via crafted EXIF data.","url":"https://insights.sbomify.com/CVE-2022-28550/"}