{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-3353 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3353 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3353 is a vulnerability."},"fix_prompt":"Check this codebase for CVE-2023-3353 and fix it if it is affected.\n\nWhat it is: CVE-2023-3353 is a vulnerability. \nExploitation: There is no known exploitation of CVE-2023-3353 in the wild and no public exploit code.\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-2023-3353/ (Markdown: https://insights.sbomify.com/CVE-2023-3353/index.md)","id":"CVE-2023-3353","markdown":"https://insights.sbomify.com/CVE-2023-3353/index.md","name":"CVE-2023-3353","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"Wordfence","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"** REJECT ** Developer patched two issues with a single patch, so only one CVE is necessary. Please use CVE-2023-3352.","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":"** REJECT ** Developer patched two issues with a single patch, so only one CVE is necessary.","id":"CVE-2023-3353","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2023"},"n_packages":0,"n_references":0,"next":{"headline":"Improper i/o watch removal in tls handshake can lead to remote unauthenticated denial of service","id":"CVE-2023-3354"},"packages":[],"prev":{"headline":"Smush – Lazy Load Images, Optimize \u0026 Compress Images \u003c= 3.16.4 - Missing Authorization to Resmush List Deletion","id":"CVE-2023-3352"},"products":[],"published":null,"related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2024-06-20","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2023-3353/"}