CVE-2021-44510

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.

Published: 2022-04-15 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-44510 is rated Moderate Risk (40.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.12%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-44510

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-17 0.26% 0.12% -0.14%
2 2025-11-21 0.37% 0.26% -0.10%
3 2025-11-18 — 0.37% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-44510

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2021-44510

OS Trackers for CVE-2021-44510

vendor priority summary link
debian not yet assigned CVE-2021-44510 not yet assigned priority: Debian including 1 source packages (fis-gtm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2021-44510
ubuntu low CVE-2021-44510 low priority: Ubuntu including 1 source packages (fis-gtm), 13 status rows across 13 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, upstream, xenial): released 5, ignored 4, not-affected 4. https://ubuntu.com/security/CVE-2021-44510

Affected software / configurations for CVE-2021-44510

Vendor Product Version Raw CPE
fisglobal gt.m <= 7.0-000 cpe:2.3:a:fisglobal:gt.m:*:*:*:*:*:*:*:*

References for CVE-2021-44510

URL Tags
http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-002_Release_Notes.html Release Notes Third Party Advisory
https://gitlab.com/YottaDB/DB/YDB/-/issues/828 Issue Tracking Patch Third Party Advisory
https://sourceforge.net/projects/fis-gtm/files/ Product Third Party Advisory
cvelogic Threat Intelligence