{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1356 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2006-1356 is a medium-severity memory corruption vulnerability in n/a, published on 22 Mar 2006. 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-2006-1356 and fix it if it is affected.\n\nWhat it is: CVE-2006-1356 is a medium-severity memory corruption vulnerability in n/a, published on 22 Mar 2006. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1356 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-2006-1356/ (Markdown: https://insights.sbomify.com/CVE-2006-1356/index.md)","id":"CVE-2006-1356","markdown":"https://insights.sbomify.com/CVE-2006-1356/index.md","name":"CVE-2006-1356","record":{"aliases":["DEBIAN-CVE-2006-1356","GHSA-q25q-j6qv-cjrj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LibVC library","requires_auth":"none","summary":"A stack-based buffer overflow in LibVC allows attackers to execute arbitrary code via a malicious vCard file, requiring user interaction to open the file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libvc","vendor":"andrew_hsu"},{"product":"rolo","vendor":"andrew_hsu"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Stack-based buffer overflow in the count_vcards function in LibVC 3, as used in Rolo, allows user-assisted attackers to execute arbitrary code via a vCard file (e.g. contacts.vcf) containing a long line.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-03-21","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-03-21","kind":"exploitdb","ref":"27474","stars":null,"title":"LibVC - '.VCard' 003 Processing Buffer Overflow"}],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2006-1356","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-1357"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2006-1355"},"products":["n/a"],"published":"2006-03-22","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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"A stack-based buffer overflow in LibVC allows attackers to execute arbitrary code via a malicious vCard file, requiring user interaction to open the file.","url":"https://insights.sbomify.com/CVE-2006-1356/"}