{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-1623 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2013-1623 is a medium-severity vulnerability in n/a, published on 8 Feb 2013."},"fix_prompt":"Check this codebase for CVE-2013-1623 and fix it if it is affected.\n\nWhat it is: CVE-2013-1623 is a medium-severity vulnerability in n/a, published on 8 Feb 2013. \nExploitation: There is no known exploitation of CVE-2013-1623 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-2013-1623/ (Markdown: https://insights.sbomify.com/CVE-2013-1623/index.md)","id":"CVE-2013-1623","markdown":"https://insights.sbomify.com/CVE-2013-1623/index.md","name":"CVE-2013-1623","record":{"aliases":["GHSA-5g8p-qpcj-85w5"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"cyassl","vendor":"yassl"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"The TLS and DTLS implementations in wolfSSL CyaSSL before 2.5.0 do not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169.","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":"The TLS and DTLS implementations in wolfSSL CyaSSL before 2.5.0 do not properly consider timing side-channel attacks on a noncompliant MAC c","id":"CVE-2013-1623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2013"},"n_packages":0,"n_references":5,"next":{"headline":"Improper Input Validation in Bouncy Castle","id":"CVE-2013-1624"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2013-1622"},"products":["n/a"],"published":"2013-02-08","related":[{"cvss_score":5.8,"headline":"Security feature bypass in n/a","id":"CVE-2014-2900","kev_date_added":null,"published":"2014-04-22"},{"cvss_score":5,"headline":"Null dereference in n/a","id":"CVE-2014-2899","kev_date_added":null,"published":"2014-04-22"},{"cvss_score":5,"headline":"Null dereference in n/a","id":"CVE-2012-1558","kev_date_added":null,"published":"2012-03-12"}],"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-06","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2013-1623/"}