{"answers":{"affected":"It affects 19 products.","exploited":"There is no known exploitation of CVE-2024-39921 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-39921 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-39921 is a high-severity vulnerability in Fsas Technologies Inc. IPCOM EX2 Series, published on 4 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39921 and fix it if it is affected.\n\nWhat it is: CVE-2024-39921 is a high-severity vulnerability in Fsas Technologies Inc. IPCOM EX2 Series, published on 4 Sep 2024. 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-2024-39921 in the wild and no public exploit code.\n\nAffected product: Fsas Technologies Inc. IPCOM EX2 Series. 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-2024-39921/ (Markdown: https://insights.sbomify.com/CVE-2024-39921/index.md)","id":"CVE-2024-39921","markdown":"https://insights.sbomify.com/CVE-2024-39921/index.md","name":"CVE-2024-39921","record":{"aliases":["GHSA-c5j5-cf8h-96p6"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IPCOM network device","requires_auth":"none","summary":"An attacker can decrypt encrypted communications on IPCOM EX2 and VE2 series devices due to observable timing discrepancies.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"ipcom_ex2_dc_3200_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_dc_3500_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_in_3200_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_in_3500_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_lb_3200_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_lb_3500_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_sc_3200_firmware","vendor":"fujitsu"},{"product":"ipcom_ex2_sc_3500_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_100_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_200_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_220_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_plus2_200_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_plus2_220_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_plus_100_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_plus_200_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_ls_plus_220_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_sc_plus_100_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_sc_plus_200_firmware","vendor":"fujitsu"},{"product":"ipcom_ve2_sc_plus_220_firmware","vendor":"fujitsu"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Observable timing discrepancy issue exists in IPCOM EX2 Series V01L02NF0001 to V01L06NF0401, V01L20NF0001 to V01L20NF0401, V02L20NF0001 to V02L21NF0301, and IPCOM VE2 Series V01L04NF0001 to V01L06NF0112. If this vulnerability is exploited, some of the encrypted communication may be decrypted by an attacker who can obtain the contents of the communication.","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":"Information disclosure in IPCOM EX2 Series","id":"CVE-2024-39921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in LOGO! 12/24RCE","id":"CVE-2024-39922"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2024-39920"},"products":["IPCOM EX2 Series","IPCOM VE2 Series"],"published":"2024-09-04","related":[{"cvss_score":9.8,"headline":"Command injection in IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 series","id":"CVE-2022-29516","kev_date_added":null,"published":"2022-05-18"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["Fsas Technologies Inc."]},"summary":"An attacker can decrypt encrypted communications on IPCOM EX2 and VE2 series devices due to observable timing discrepancies.","url":"https://insights.sbomify.com/CVE-2024-39921/"}