# CVE-2015-2616: Denial of service in n/a

> Local attackers can cause a denial of service in Oracle Sun Solaris via unspecified DevFS vectors.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3wq2-hvxm-x2c4

## What is CVE-2015-2616?

CVE-2015-2616 is a medium-severity denial of service vulnerability in n/a, published on 16 Jul 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in Oracle Sun Solaris 3.3 and 4.2 allows local users to affect availability via unknown vectors related to DevFS.

## Which versions are affected by CVE-2015-2616?

It affects 1 product.


Products: Oracle Oracle and Sun Systems Product Suite.

## How do I fix CVE-2015-2616?

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

## Is CVE-2015-2616 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4915](https://insights.sbomify.com/CVE-2015-4915/): Other in n/a (critical 10.0)
- [CVE-2015-4821](https://insights.sbomify.com/CVE-2015-4821/): Other in n/a (critical 9.3)
- [CVE-2014-4259](https://insights.sbomify.com/CVE-2014-4259/): Other in n/a (critical 9.0)
- [CVE-2013-3746](https://insights.sbomify.com/CVE-2013-3746/): Other in n/a (high 7.2)
- [CVE-2013-3754](https://insights.sbomify.com/CVE-2013-3754/): Other in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2616 and fix it if it is affected.

What it is: CVE-2015-2616 is a medium-severity denial of service vulnerability in n/a, published on 16 Jul 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2616 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-2015-2616/ (Markdown: https://insights.sbomify.com/CVE-2015-2616/index.md)
```

## Sources

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

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