# CVE-2021-44508: Null dereference in n/a

> Attackers can crash the FIS GT.M database application by triggering a NULL pointer dereference in the ious_open function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-44508, GHSA-qc3r-f2r4-qcc5, UBUNTU-CVE-2021-44508

## What is CVE-2021-44508?

CVE-2021-44508 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.

### Official description

An issue was discovered in FIS GT.M through V7.0-000 (related to the YottaDB code base). A lack of NULL checks in calls to ious_open in sr_unix/ious_open.c allows attackers to crash the application by dereferencing a NULL pointer.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2021-44508?

It affects 1 product.


Products: Fisglobal Gt.m.

## How do I fix CVE-2021-44508?

Apply the vendor's patch.

## Is CVE-2021-44508 being exploited?

There is no known exploitation of CVE-2021-44508 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-44486](https://insights.sbomify.com/CVE-2021-44486/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-44496](https://insights.sbomify.com/CVE-2021-44496/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-44488](https://insights.sbomify.com/CVE-2021-44488/): Memory corruption in n/a (critical 9.1)
- [CVE-2021-44481](https://insights.sbomify.com/CVE-2021-44481/): Null dereference in n/a (high 7.5)
- [CVE-2021-44482](https://insights.sbomify.com/CVE-2021-44482/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44508 and fix it if it is affected.

What it is: CVE-2021-44508 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.
Exploitation: There is no known exploitation of CVE-2021-44508 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-44508/ (Markdown: https://insights.sbomify.com/CVE-2021-44508/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-44508
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-44508
- OSV: https://osv.dev/vulnerability/CVE-2021-44508

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-44508/
Summaries are generated and may contain mistakes; the official description above is the record.