# CVE-2002-1221: Null dereference in n/a

> Remote attackers can crash the BIND DNS server by sending SIG records with invalid expiry times, causing a null pointer dereference.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6qgf-gfj4-gj5c

## What is CVE-2002-1221?

CVE-2002-1221 is a medium-severity vulnerability in Freebsd Freebsd, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BIND 8.x through 8.3.3 allows remote attackers to cause a denial of service (crash) via SIG RR elements with invalid expiry times, which are removed from the internal BIND database and later cause a null dereference.

## Which versions are affected by CVE-2002-1221?

It affects 3 products.


Products: Freebsd Freebsd, Isc Bind, Openbsd Openbsd.

## How do I fix CVE-2002-1221?

Upgrade to a fixed version.

## Is CVE-2002-1221 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1221 and fix it if it is affected.

What it is: CVE-2002-1221 is a medium-severity vulnerability in Freebsd Freebsd, published on 1 Sep 2004. 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-2002-1221 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-2002-1221/ (Markdown: https://insights.sbomify.com/CVE-2002-1221/index.md)
```

## Sources

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

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