{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-52427 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-52427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-52427 is a high-severity denial of service vulnerability in n/a, published on 11 Feb 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-2023-52427 and fix it if it is affected.\n\nWhat it is: CVE-2023-52427 is a high-severity denial of service vulnerability in n/a, published on 11 Feb 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-2023-52427 in the wild and no public exploit code.\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-52427/ (Markdown: https://insights.sbomify.com/CVE-2023-52427/index.md)","id":"CVE-2023-52427","markdown":"https://insights.sbomify.com/CVE-2023-52427/index.md","name":"CVE-2023-52427","record":{"aliases":["GHSA-h7x2-hfmv-h4xf"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenDDS library","requires_auth":"none","summary":"A segmentation fault occurs in OpenDDS when a DataWriter is configured with an excessively large max_samples value, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opendds","vendor":"objectcomputing"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","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-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"In OpenDDS through 3.27, there is a segmentation fault for a DataWriter with a large value of resource_limits.max_samples. NOTE: the vendor's position is that the product is not designed to handle a max_samples value that is too large for the amount of memory on the system.","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":"Denial of service in n/a","id":"CVE-2023-52427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of Service in Connect2id Nimbus JOSE+JWT","id":"CVE-2023-52428"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2023-52426"},"products":["n/a"],"published":"2024-02-11","related":[{"cvss_score":8.6,"headline":"OCI OpenDDS Secure Amplification","id":"CVE-2021-38447","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2025-67111","kev_date_added":null,"published":"2025-12-23"},{"cvss_score":7.5,"headline":"Malformed PID_PROPERTY_LIST parameter in DATA submessage remotely crashes OpenDDS","id":"CVE-2023-37915","kev_date_added":null,"published":"2023-07-21"},{"cvss_score":7,"headline":"OCI OpenDDS Secure Improper Handling of Length Parameter Inconsistency","id":"CVE-2021-38445","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":6.6,"headline":"OCI OpenDDS Secure Network Amplification","id":"CVE-2021-38429","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":5.3,"headline":"Specially crafted RTPS message may cause an OpenDDS application to crash","id":"CVE-2023-23932","kev_date_added":null,"published":"2023-02-03"}],"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":"2024-08-02","vendors":["n/a"]},"summary":"A segmentation fault occurs in OpenDDS when a DataWriter is configured with an excessively large max_samples value, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2023-52427/"}