{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32543 exists.","fix":"No fix has been published for CVE-2022-32543 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-32543 is a high-severity vulnerability in ESTsoft Alyac, published on 5 Aug 2022. 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-2022-32543 and fix it if it is affected.\n\nWhat it is: CVE-2022-32543 is a high-severity vulnerability in ESTsoft Alyac, published on 5 Aug 2022. 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-2022-32543 exists.\n\nAffected product: ESTsoft Alyac. 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-32543/ (Markdown: https://insights.sbomify.com/CVE-2022-32543/index.md)","id":"CVE-2022-32543","markdown":"https://insights.sbomify.com/CVE-2022-32543/index.md","name":"CVE-2022-32543","record":{"aliases":["GHSA-3r68-64pc-x636"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Alyac antivirus","requires_auth":"low_privilege","summary":"A specially crafted OLE file can trigger an integer overflow leading to heap buffer overflow and arbitrary code execution in ESTsoft Alyac.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"alyac","vendor":"estsoft"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-680","name":"Integer Overflow to Buffer Overflow"}],"description":"An integer overflow vulnerability exists in the way ESTsoft Alyac 2.5.8.544 parses OLE files. A specially-crafted OLE file can lead to a heap buffer overflow which can result in arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in Alyac","id":"CVE-2022-32543","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Cybozu Office","id":"CVE-2022-32544"},"packages":[],"prev":{"headline":"Information disclosure in BVMS","id":"CVE-2022-32540"},"products":["Alyac"],"published":"2022-08-05","related":[{"cvss_score":7.3,"headline":"Integer overflow in Alyac","id":"CVE-2022-29886","kev_date_added":null,"published":"2022-08-05"},{"cvss_score":5,"headline":"Denial of service in Alyac","id":"CVE-2022-43665","kev_date_added":null,"published":"2023-02-02"},{"cvss_score":5,"headline":"Memory corruption in Alyac","id":"CVE-2022-21147","kev_date_added":null,"published":"2022-05-12"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["ESTsoft"]},"summary":"A specially crafted OLE file can trigger an integer overflow leading to heap buffer overflow and arbitrary code execution in ESTsoft Alyac.","url":"https://insights.sbomify.com/CVE-2022-32543/"}