{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55081 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55081 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55081 is a medium-severity memory corruption vulnerability in Eclipse Foundation NetX Duo, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55081 and fix it if it is affected.\n\nWhat it is: CVE-2025-55081 is a medium-severity memory corruption vulnerability in Eclipse Foundation NetX Duo, published on 15 Oct 2025. 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-2025-55081 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation NetX Duo. 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-2025-55081/ (Markdown: https://insights.sbomify.com/CVE-2025-55081/index.md)","id":"CVE-2025-55081","markdown":"https://insights.sbomify.com/CVE-2025-55081/index.md","name":"CVE-2025-55081","record":{"aliases":["GHSA-5vrv-8j5h-h6h6"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ThreadX RTOS TLS","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds read in the TLS client hello processing, potentially causing a denial of service or information disclosure in ThreadX RTOS.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"threadx_netx_duo","vendor":"eclipse"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-126","name":"Buffer Over-read"}],"description":"In Eclipse Foundation NextX Duo before 6.4.4, a module of ThreadX, the _nx_secure_tls_process_clienthello() function was missing length verification of \ncertain SSL/TLS client hello message: the ciphersuite length and \ncompression method length. In case of an attacker-crafted message with \nvalues outside of the expected range, it could cause an out-of-bound \nread.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Potential out of bound read in _nx_secure_tls_process_clienthello()","id":"CVE-2025-55081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Potential out of bound read and info leak in_nx_secure_tls_psk_identity_find()","id":"CVE-2025-55082"},"packages":[],"prev":{"headline":"Improper Parameter Check in ThreadX Syscall Implementation","id":"CVE-2025-55080"},"products":["NetX Duo"],"published":"2025-10-15","related":[{"cvss_score":8.8,"headline":"Web http client: Unchecked Server-Side Malicious Packet Issue","id":"CVE-2025-55085","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":8.7,"headline":"Denial of service in Eclipse ThreadX - NetX Duo","id":"CVE-2025-55102","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":7.5,"headline":"Memory corruption in Eclipse ThreadX - NetX Duo","id":"CVE-2026-11576","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":7.1,"headline":"Eclipse ThreadX NetX Duo HTTP component server denial of service","id":"CVE-2025-2260","kev_date_added":null,"published":"2025-04-06"},{"cvss_score":7.1,"headline":"Eclipse ThreadX NetX Duo HTTP server denial of service","id":"CVE-2025-0726","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":7,"headline":"Integer wraparound, under-allocation, and heap buffer overflow in Eclipse ThreadX NetX Duo __portable_aligned_alloc()","id":"CVE-2024-2452","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":6.9,"headline":"Potential out of bound read in _nx_ipv4_option_process()","id":"CVE-2025-55092","kev_date_added":null,"published":"2025-10-17"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["Eclipse Foundation"]},"summary":"An attacker can trigger an out-of-bounds read in the TLS client hello processing, potentially causing a denial of service or information disclosure in ThreadX RTOS.","url":"https://insights.sbomify.com/CVE-2025-55081/"}