{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44510 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-44510 is a high-severity vulnerability in n/a, published on 15 Apr 2022. 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-44510 and fix it if it is affected.\n\nWhat it is: CVE-2021-44510 is a high-severity vulnerability in n/a, published on 15 Apr 2022. 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-44510 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-2021-44510/ (Markdown: https://insights.sbomify.com/CVE-2021-44510/index.md)","id":"CVE-2021-44510","markdown":"https://insights.sbomify.com/CVE-2021-44510/index.md","name":"CVE-2021-44510","record":{"aliases":["DEBIAN-CVE-2021-44510","GHSA-gwwv-284v-w5c5","UBUNTU-CVE-2021-44510"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FIS GT.M database","requires_auth":"none","summary":"Attackers can cause a segmentation fault and crash the application by triggering an integer overflow in memset size calculations.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gt.m","vendor":"fisglobal"}],"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-131","name":"Incorrect Calculation of Buffer Size"}],"description":"An issue was discovered in FIS GT.M through V7.0-000 (related to the YottaDB code base). Using crafted input, attackers can cause a calculation of the size of calls to memset in op_fnj3 in sr_port/op_fnj3.c to result in an extremely large value in order to cause a segmentation fault and crash the application.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Integer overflow in n/a","id":"CVE-2021-44510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2021-44512"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2021-44509"},"products":["n/a"],"published":"2022-04-15","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44486","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44496","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2021-44488","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2021-44481","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2021-44482","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-44483","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2021-44484","kev_date_added":null,"published":"2022-04-15"}],"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-08-04","vendors":["n/a"]},"summary":"Attackers can cause a segmentation fault and crash the application by triggering an integer overflow in memset size calculations.","url":"https://insights.sbomify.com/CVE-2021-44510/"}