{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23119 exists.","fix":"No fix has been published for CVE-2023-23119 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-23119 is a medium-severity vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-23119 and fix it if it is affected.\n\nWhat it is: CVE-2023-23119 is a medium-severity vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23119 exists.\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-2023-23119/ (Markdown: https://insights.sbomify.com/CVE-2023-23119/index.md)","id":"CVE-2023-23119","markdown":"https://insights.sbomify.com/CVE-2023-23119/index.md","name":"CVE-2023-23119","record":{"aliases":["GHSA-c4v2-98hc-pvh9"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ubiquiti airFiber radio","requires_auth":"none","summary":"An attacker can bypass firmware integrity checks via MITM to install malicious firmware on Ubiquiti airFiber radios.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"af-2x_firmware","vendor":"ui"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes Ubiquiti airFiber AF2X Radio firmware version 3.2.2 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new firmware image and bypass the checksum verification.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2023-23119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2023-23120"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2023-23110"},"products":["n/a"],"published":"2023-02-02","related":[],"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-03-26","vendors":["n/a"]},"summary":"An attacker can bypass firmware integrity checks via MITM to install malicious firmware on Ubiquiti airFiber radios.","url":"https://insights.sbomify.com/CVE-2023-23119/"}