{"answers":{"affected":"It affects 15 products.","exploited":"There is no known exploitation of CVE-2021-21005 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21005 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21005 is a high-severity vulnerability in Phoenix Contact FL NAT, published on 25 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21005 and fix it if it is affected.\n\nWhat it is: CVE-2021-21005 is a high-severity vulnerability in Phoenix Contact FL NAT, published on 25 Jun 2021. 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-2021-21005 in the wild and no public exploit code.\n\nAffected product: Phoenix Contact FL NAT. 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-2021-21005/ (Markdown: https://insights.sbomify.com/CVE-2021-21005/index.md)","id":"CVE-2021-21005","markdown":"https://insights.sbomify.com/CVE-2021-21005/index.md","name":"CVE-2021-21005","record":{"aliases":["GHSA-jmcx-w32h-8qj4"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial network switch","requires_auth":"none","summary":"An attacker can crash Phoenix Contact FL SWITCH devices by sending a crafted TCP packet, requiring a reboot to restore service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"fl_nat_smn_8tx-m_firmware","vendor":"phoenixcontact"},{"product":"fl_nat_smn_8tx_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_14tx\\/2fx-sm_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_14tx\\/2fx_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_16tx_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_4tx-pn_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_6gt\\/2sfp_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_6tx\\/2sfp_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_8gt_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_8tx-pn_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smcs_8tx_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smn_6tx\\/2fx_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smn_6tx\\/2fx_sm_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smn_6tx\\/2pof-pn_firmware","vendor":"phoenixcontact"},{"product":"fl_switch_smn_8tx-pn_firmware","vendor":"phoenixcontact"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In Phoenix Contact FL SWITCH SMCS series products in multiple versions if an attacker sends a hand-crafted TCP-Packet with the Urgent-Flag set and the Urgent-Pointer set to 0, the network stack will crash. The device needs to be rebooted afterwards.","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":"Race Condition Vulnerability in Phoenix Contact FL SWITCH SMCS series products","id":"CVE-2021-21005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Heap buffer overflow when handling crafted font file could lead to arbitrary code execution","id":"CVE-2021-21006"},"packages":[],"prev":{"headline":"Cross-site Scripting Vulnerability in Phoenix Contact FL SWITCH SMCS series products","id":"CVE-2021-21004"},"products":["FL NAT","FL SWITCH"],"published":"2021-06-25","related":[{"cvss_score":7.4,"headline":"Cross-site Scripting Vulnerability in Phoenix Contact FL SWITCH SMCS series products","id":"CVE-2021-21004","kev_date_added":null,"published":"2021-06-25"},{"cvss_score":5.3,"headline":"Denial of Service Vulnerability in Phoenix Contact FL SWITCH SMCS series products","id":"CVE-2021-21003","kev_date_added":null,"published":"2021-06-25"}],"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":["Phoenix Contact"]},"summary":"An attacker can crash Phoenix Contact FL SWITCH devices by sending a crafted TCP packet, requiring a reboot to restore service.","url":"https://insights.sbomify.com/CVE-2021-21005/"}