{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41581 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41581 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41581 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2021. 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-41581 and fix it if it is affected.\n\nWhat it is: CVE-2021-41581 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2021. 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-41581 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-2021-41581/ (Markdown: https://insights.sbomify.com/CVE-2021-41581/index.md)","id":"CVE-2021-41581","markdown":"https://insights.sbomify.com/CVE-2021-41581/index.md","name":"CVE-2021-41581","record":{"aliases":["GHSA-675w-hmxx-cvf3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LibreSSL crypto library","requires_auth":"none","summary":"A stack-based buffer over-read in LibreSSL's X.509 constraint parser can cause crashes or leak memory when processing malformed inputs.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libressl","vendor":"openbsd"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"x509_constraints_parse_mailbox in lib/libcrypto/x509/x509_constraints.c in LibreSSL through 3.4.0 has a stack-based buffer over-read. When the input exceeds DOMAIN_PART_MAX_LEN, the buffer lacks '\\0' termination.","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-2021-41581","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2021-41583"},"packages":[],"prev":{"headline":"Improper Access Control in passport-oauth2","id":"CVE-2021-41580"},"products":["n/a"],"published":"2021-09-24","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2023-35784","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-46880","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in LibreSSL","id":"CVE-2015-5334","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":7.5,"headline":"Denial of service in LibreSSL","id":"CVE-2015-5333","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2014-9424","kev_date_added":null,"published":"2014-12-29"},{"cvss_score":7.4,"headline":"Security feature bypass in n/a","id":"CVE-2018-8970","kev_date_added":null,"published":"2018-03-24"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2019-25048","kev_date_added":null,"published":"2021-07-01"}],"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-04","vendors":["n/a"]},"summary":"A stack-based buffer over-read in LibreSSL's X.509 constraint parser can cause crashes or leak memory when processing malformed inputs.","url":"https://insights.sbomify.com/CVE-2021-41581/"}