{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36316 is a medium-severity memory corruption vulnerability in n/a, published on 7 Apr 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-2020-36316 and fix it if it is affected.\n\nWhat it is: CVE-2020-36316 is a medium-severity memory corruption vulnerability in n/a, published on 7 Apr 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-2020-36316 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-2020-36316/ (Markdown: https://insights.sbomify.com/CVE-2020-36316/index.md)","id":"CVE-2020-36316","markdown":"https://insights.sbomify.com/CVE-2020-36316/index.md","name":"CVE-2020-36316","record":{"aliases":["GHSA-f5m2-hpp5-7qp7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RELIC cryptographic library","requires_auth":"none","summary":"A buffer overflow in RELIC's PKCS#1 v1.5 signature verification allows attackers to cause memory corruption via crafted garbage bytes.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"relic","vendor":"relic_project"}],"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-120","name":"Buffer Copy without Checking Size of Input"}],"description":"In RELIC before 2021-04-03, there is a buffer overflow in PKCS#1 v1.5 signature verification because garbage bytes can be present.","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-2020-36316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-36317"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2020-36315"},"products":["n/a"],"published":"2021-04-07","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2023-36326","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2023-36327","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2023-51939","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":5.3,"headline":"Weak cryptography in n/a","id":"CVE-2020-36315","kev_date_added":null,"published":"2021-04-07"}],"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 buffer overflow in RELIC's PKCS#1 v1.5 signature verification allows attackers to cause memory corruption via crafted garbage bytes.","url":"https://insights.sbomify.com/CVE-2020-36316/"}