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

> Attackers can cause a denial of service by triggering a null pointer dereference in YottaDB due to lack of input validation.

- **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:** No
- **Published:** 15 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r33v-p75h-gjjw, UBUNTU-CVE-2021-44482

## What is CVE-2021-44482?

CVE-2021-44482 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 YottaDB through r1.32 and V7.0-000. A lack of input validation in calls to do_verify in sr_unix/do_verify.c allows attackers to attempt to jump to a NULL pointer by corrupting a function pointer.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Fisglobal Gt.m, Yottadb Yottadb.

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

No fix has been published for CVE-2021-44482 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-44482 being exploited?

There is no known exploitation of CVE-2021-44482 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-44483](https://insights.sbomify.com/CVE-2021-44483/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-44482 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-44482 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-44482/ (Markdown: https://insights.sbomify.com/CVE-2021-44482/index.md)
```

## Sources

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

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