# CVE-2014-9491: Null dereference in n/a

> Remote attackers can cause a denial of service in illumos via a NULL pointer dereference in the devzvol_readdir function.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vr47-prxx-24cf

## What is CVE-2014-9491?

CVE-2014-9491 is a medium-severity vulnerability in n/a, published on 20 Jan 2015. It can be exploited over the network, with no action from the victim.

### Official description

The devzvol_readdir function in illumos does not check the return value of a strchr call, which allows remote attackers to cause a denial of service (NULL pointer dereference and panic) via unspecified vectors.

## Which versions are affected by CVE-2014-9491?

It affects 1 product.


Products: Illumos Illumos.

## How do I fix CVE-2014-9491?

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

## Is CVE-2014-9491 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-27678](https://insights.sbomify.com/CVE-2020-27678/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-6560](https://insights.sbomify.com/CVE-2016-6560/): Integer overflow in osnet-incorporation (high 8.6)
- [CVE-2019-9579](https://insights.sbomify.com/CVE-2019-9579/): Missing authorization in n/a (high 8.1)
- [CVE-2016-6561](https://insights.sbomify.com/CVE-2016-6561/): Null dereference in osnet-incorporation (high 7.5)
- [CVE-2021-43395](https://insights.sbomify.com/CVE-2021-43395/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9491 and fix it if it is affected.

What it is: CVE-2014-9491 is a medium-severity vulnerability in n/a, published on 20 Jan 2015. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9491 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-2014-9491/ (Markdown: https://insights.sbomify.com/CVE-2014-9491/index.md)
```

## Sources

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

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