{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-26305 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2022-26305 is a high-severity vulnerability in Libreoffice Libreoffice, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-26305 and fix it if it is affected.\n\nWhat it is: CVE-2022-26305 is a high-severity vulnerability in Libreoffice Libreoffice, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-26305 in the wild and no public exploit code.\n\nAffected product: Libreoffice Libreoffice. 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-26305/ (Markdown: https://insights.sbomify.com/CVE-2022-26305/index.md)","id":"CVE-2022-26305","markdown":"https://insights.sbomify.com/CVE-2022-26305/index.md","name":"CVE-2022-26305","record":{"aliases":["DEBIAN-CVE-2022-26305","GHSA-fm9c-xcj2-2j5g","UBUNTU-CVE-2022-26305"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreOffice","requires_auth":"none","summary":"Attackers can bypass macro trust checks by spoofing certificate details, tricking users into executing malicious code in LibreOffice.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Document Fdn.","cpe":[{"product":"libreoffice","vendor":"libreoffice"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An Improper Certificate Validation vulnerability in LibreOffice existed where determining if a macro was signed by a trusted author was done by only matching the serial number and issuer string of the used certificate with that of a trusted certificate. This is not sufficient to verify that the macro was actually signed with the certificate. An adversary could therefore create an arbitrary certificate with a serial number and an issuer string identical to a trusted certificate which LibreOffice would present as belonging to the trusted author, potentially leading to the user to execute arbitrary code contained in macros improperly trusted. This issue affects: The Document Foundation LibreOffice 7.2 versions prior to 7.2.7; 7.3 versions prior to 7.3.1.","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":"Execution of Untrusted Macros Due to Improper Certificate Validation","id":"CVE-2022-26305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libreoffice:libreoffice","products":["libreoffice:libreoffice"],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Execution of Untrusted Macros Due to Improper Certificate Validation","id":"CVE-2022-26306"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2022-26304"},"products":["LibreOffice"],"published":"2022-07-25","related":[{"cvss_score":10,"headline":"TLS certificate are not properly verified when utilizing LibreOfficeKit","id":"CVE-2024-5261","kev_date_added":null,"published":"2024-06-25"},{"cvss_score":9.8,"headline":"Windows 8.3 path equivalence handling flaw allows LibreLogo script execution","id":"CVE-2019-9855","kev_date_added":null,"published":"2019-09-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14939","kev_date_added":null,"published":"2018-08-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8358","kev_date_added":null,"published":"2017-04-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7882","kev_date_added":null,"published":"2017-04-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-10327","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7856","kev_date_added":null,"published":"2017-04-14"}],"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":["The Document Foundation"]},"summary":"Attackers can bypass macro trust checks by spoofing certificate details, tricking users into executing malicious code in LibreOffice.","url":"https://insights.sbomify.com/CVE-2022-26305/"}