{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39173 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2022-39173 is a high-severity vulnerability in Wolfssl Wolfssl, published on 29 Sep 2022."},"fix_prompt":"Check this codebase for CVE-2022-39173 and fix it if it is affected.\n\nWhat it is: CVE-2022-39173 is a high-severity vulnerability in Wolfssl Wolfssl, published on 29 Sep 2022. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39173 exists.\n\nAffected product: Wolfssl Wolfssl. 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-2022-39173/ (Markdown: https://insights.sbomify.com/CVE-2022-39173/index.md)","id":"CVE-2022-39173","markdown":"https://insights.sbomify.com/CVE-2022-39173/index.md","name":"CVE-2022-39173","record":{"aliases":["DEBIAN-CVE-2022-39173","GHSA-ww6v-6x26-hgfc","JLSEC-2026-673","UBUNTU-CVE-2022-39173"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"wolfssl","vendor":"wolfssl"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3 handshake. This occurs when an attacker supposedly resumes a previous TLS session. During the resumption Client Hello a Hello Retry Request must be triggered. Both Client Hellos are required to contain a list of duplicate cipher suites to trigger the buffer overflow. In total, two Client Hellos have to be sent: one in the resumed session, and a second one as a response to a Hello Retry Request message.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3 handshake.","id":"CVE-2022-39173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wolfssl:wolfssl","products":["wolfssl:wolfssl"],"type":null,"year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-39176"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-39172"},"products":["n/a"],"published":"2022-09-29","related":[{"cvss_score":10,"headline":"Buffer overread in domain name matching","id":"CVE-2024-5991","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2021-37155","kev_date_added":null,"published":"2021-07-21"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-36177","kev_date_added":null,"published":"2021-01-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-2896","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-2897","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2014-2898","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-16748","kev_date_added":null,"published":"2019-09-24"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-20","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2022-39173/"}