{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000416 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1000416 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1000416 is a medium-severity vulnerability in n/a, published on 22 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-1000416 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000416 is a medium-severity vulnerability in n/a, published on 22 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-1000416 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-1000416/ (Markdown: https://insights.sbomify.com/CVE-2017-1000416/index.md)","id":"CVE-2017-1000416","markdown":"https://insights.sbomify.com/CVE-2017-1000416/index.md","name":"CVE-2017-1000416","record":{"aliases":["GHSA-56mf-wc59-ghx4"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TLS library","requires_auth":"none","summary":"A coding error in axTLS misinterprets specific UTCTime values, potentially allowing certificate validation bypasses or logic errors in TLS implementations.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"axtls","vendor":"axtls_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-193","name":"Off-by-one Error"}],"description":"axTLS version 1.5.3 has a coding error in the ASN.1 parser resulting in the year (19)50 of UTCTime being misinterpreted as 2050.","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":"Other in n/a","id":"CVE-2017-1000416","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2017-1000417"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2017-1000415"},"products":["n/a"],"published":"2018-01-22","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-8981","kev_date_added":null,"published":"2019-03-26"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-10013","kev_date_added":null,"published":"2019-12-03"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-9689","kev_date_added":null,"published":"2019-12-03"},{"cvss_score":5.9,"headline":"Memory corruption in n/a","id":"CVE-2018-16149","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":5.9,"headline":"Weak cryptography in n/a","id":"CVE-2018-16150","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":5.9,"headline":"Security feature bypass in n/a","id":"CVE-2018-16253","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2023-33613","kev_date_added":null,"published":"2023-06-06"}],"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-17","vendors":["n/a"]},"summary":"A coding error in axTLS misinterprets specific UTCTime values, potentially allowing certificate validation bypasses or logic errors in TLS implementations.","url":"https://insights.sbomify.com/CVE-2017-1000416/"}