{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000415 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1000415 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1000415 is a medium-severity vulnerability in n/a, published on 9 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000415 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000415 is a medium-severity vulnerability in n/a, published on 9 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000415 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-2017-1000415/ (Markdown: https://insights.sbomify.com/CVE-2017-1000415/index.md)","id":"CVE-2017-1000415","markdown":"https://insights.sbomify.com/CVE-2017-1000415/index.md","name":"CVE-2017-1000415","record":{"aliases":["GHSA-gc7h-mj38-j8xm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MatrixSSL library","requires_auth":"none","summary":"Attackers can bypass certificate expiration checks due to incorrect date validation, allowing the use of expired certificates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"matrixssl","vendor":"matrixssl"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"MatrixSSL version 3.7.2 has an incorrect UTCTime date range validation in its X.509 certificate validation process resulting in some certificates have their expiration (beginning) year extended (delayed) by 100 years.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2017-1000415","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2017-1000416"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-1000414"},"products":["n/a"],"published":"2018-01-09","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14431","kev_date_added":null,"published":"2019-07-29"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-13470","kev_date_added":null,"published":"2019-07-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-10914","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-6890","kev_date_added":null,"published":"2017-01-05"},{"cvss_score":8.1,"headline":"Integer overflow in n/a","id":"CVE-2022-43974","kev_date_added":null,"published":"2023-01-09"},{"cvss_score":8.1,"headline":"Memory corruption in MatrixSSL","id":"CVE-2017-2780","kev_date_added":null,"published":"2017-06-22"},{"cvss_score":8.1,"headline":"Memory corruption in MatrixSSL","id":"CVE-2017-2781","kev_date_added":null,"published":"2017-06-22"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can bypass certificate expiration checks due to incorrect date validation, allowing the use of expired certificates.","url":"https://insights.sbomify.com/CVE-2017-1000415/"}