{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25635 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-25635 is a medium-severity vulnerability in Libreoffice Libreoffice, published on 21 Mar 2025. 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-2021-25635 and fix it if it is affected.\n\nWhat it is: CVE-2021-25635 is a medium-severity vulnerability in Libreoffice Libreoffice, published on 21 Mar 2025. 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: There is no known exploitation of CVE-2021-25635 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-2021-25635/ (Markdown: https://insights.sbomify.com/CVE-2021-25635/index.md)","id":"CVE-2021-25635","markdown":"https://insights.sbomify.com/CVE-2021-25635/index.md","name":"CVE-2021-25635","record":{"aliases":["GHSA-r73f-2rxh-prfm"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LibreOffice office suite","requires_auth":"none","summary":"Attackers can bypass certificate validation in LibreOffice to present modified ODF documents as validly signed by trusted parties.","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":5.2,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An Improper Certificate Validation vulnerability in LibreOffice allowed \nan attacker to self sign an ODF document, with a signature untrusted by \nthe target, then modify it to change the signature algorithm to an \ninvalid (or unknown to LibreOffice) algorithm and LibreOffice would incorrectly present such a signature with an unknown algorithm as a \nvalid signature issued by a trusted person\n\nThis issue affects LibreOffice: from 7.0 before 7.0.5, from 7.1 before 7.1.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":"Content Manipulation with Certificate Validation Attack","id":"CVE-2021-25635","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libreoffice:libreoffice","products":["libreoffice:libreoffice"],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Incorrect trust validation of signature with ambiguous KeyInfo children","id":"CVE-2021-25636"},"packages":[],"prev":{"headline":"Timestamp Manipulation with Signature Wrapping","id":"CVE-2021-25634"},"products":["LibreOffice"],"published":"2025-03-21","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-21","vendors":["The Document Foundation"]},"summary":"Attackers can bypass certificate validation in LibreOffice to present modified ODF documents as validly signed by trusted parties.","url":"https://insights.sbomify.com/CVE-2021-25635/"}