{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35506 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35506 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35506 is a high-severity memory corruption vulnerability in n/a, published on 3 Aug 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-35506 and fix it if it is affected.\n\nWhat it is: CVE-2022-35506 is a high-severity memory corruption vulnerability in n/a, published on 3 Aug 2022. 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-2022-35506 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-2022-35506/ (Markdown: https://insights.sbomify.com/CVE-2022-35506/index.md)","id":"CVE-2022-35506","markdown":"https://insights.sbomify.com/CVE-2022-35506/index.md","name":"CVE-2022-35506","record":{"aliases":["GHSA-h6p4-hc6j-x474"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TripleCross tool","requires_auth":"none","summary":"Attackers can trigger a stack overflow via unlimited program parameters, potentially causing crashes or arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"triplecross","vendor":"triplecross_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"TripleCross v0.1.0 was discovered to contain a stack overflow which occurs because there is no limit to the length of program parameters.","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":"Memory corruption in n/a","id":"CVE-2022-35506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2022-35507"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2022-35505"},"products":["n/a"],"published":"2022-08-03","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-35505","kev_date_added":null,"published":"2022-08-03"}],"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-03","vendors":["n/a"]},"summary":"Attackers can trigger a stack overflow via unlimited program parameters, potentially causing crashes or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2022-35506/"}