{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-7629 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-7629 is a critical memory corruption vulnerability in n/a, published on 18 Feb 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-7629 and fix it if it is affected.\n\nWhat it is: CVE-2019-7629 is a critical memory corruption vulnerability in n/a, published on 18 Feb 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-7629 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-7629/ (Markdown: https://insights.sbomify.com/CVE-2019-7629/index.md)","id":"CVE-2019-7629","markdown":"https://insights.sbomify.com/CVE-2019-7629/index.md","name":"CVE-2019-7629","record":{"aliases":["DEBIAN-CVE-2019-7629","GHSA-gj67-j733-78w3","UBUNTU-CVE-2019-7629"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TinTin++ MUD client","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on TinTin++ clients by sending a long message, triggering a stack-based buffer overflow.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tintin\\+\\+","vendor":"tintin\\+\\+_project"},{"product":"wintin\\+\\+","vendor":"tintin\\+\\+_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Stack-based buffer overflow in the strip_vt102_codes function in TinTin++ 2.01.6 and WinTin++ 2.01.6 allows remote attackers to execute arbitrary code by sending a long message to the client.","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":"Memory corruption in n/a","id":"CVE-2019-7629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-7630"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-7628"},"products":["n/a"],"published":"2019-02-18","related":[],"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":"Remote attackers can execute arbitrary code on TinTin++ clients by sending a long message, triggering a stack-based buffer overflow.","url":"https://insights.sbomify.com/CVE-2019-7629/"}