{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2022-29499 in the wild since at least 27 Jun 2022, including in ransomware campaigns.","fix":"No fix has been published for CVE-2022-29499 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Jul 2022.","what":"CVE-2022-29499 is a critical code injection vulnerability in n/a, published on 26 Apr 2022. 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-29499 and fix it if it is affected.\n\nWhat it is: CVE-2022-29499 is a critical code injection vulnerability in n/a, published on 26 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2022-29499 in the wild since at least 27 Jun 2022, including in ransomware campaigns.\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-29499/ (Markdown: https://insights.sbomify.com/CVE-2022-29499/index.md)","id":"CVE-2022-29499","markdown":"https://insights.sbomify.com/CVE-2022-29499/index.md","name":"CVE-2022-29499","record":{"aliases":["GHSA-f4rg-w9qm-5f42"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VoIP service appliance","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Mitel MiVoice Connect Service Appliances due to incorrect data validation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mivoice_connect","vendor":"mitel"}],"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-20","name":"Improper Input Validation"}],"description":"The Service Appliance component in Mitel MiVoice Connect through 19.2 SP3 allows remote code execution because of incorrect data validation. The Service Appliances are SA 100, SA 400, and Virtual SA.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Mitel MiVoice Connect Data Validation","id":"CVE-2022-29499","indexable":true,"kev":{"dateAdded":"2022-06-27","dueDate":"2022-07-18","knownRansomwareCampaignUse":"Known","product":"MiVoice Connect","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Mitel","vulnerabilityName":"Mitel MiVoice Connect Data Validation Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-29500"},"packages":[],"prev":{"headline":"SQL injection in blazer","id":"CVE-2022-29498"},"products":["n/a"],"published":"2022-04-26","related":[{"cvss_score":6.8,"headline":"Mitel MiVoice Connect Command Injection","id":"CVE-2022-40765","kev_date_added":"2023-02-21","published":"2022-11-22"},{"cvss_score":6.8,"headline":"Mitel MiVoice Connect Code Injection","id":"CVE-2022-41223","kev_date_added":"2023-02-21","published":"2022-11-22"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-32748","kev_date_added":null,"published":"2023-08-14"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-31457","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-31458","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-10211","kev_date_added":null,"published":"2020-04-17"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-06","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on Mitel MiVoice Connect Service Appliances due to incorrect data validation.","url":"https://insights.sbomify.com/CVE-2022-29499/"}