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

> Remote attackers can cause denial of service via infinite loops in the slapi-nis plugin by requesting groups or users with excessive members.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-0283, GHSA-mh9j-g427-6h4w

## What is CVE-2015-0283?

CVE-2015-0283 is a high-severity denial of service vulnerability in n/a, published on 30 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The slapi-nis plug-in before 0.54.2 does not properly reallocate memory when processing user accounts, which allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a request for a (1) group with a large number of members or (2) user that belongs to a large number of groups.

Weakness: CWE-399

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

It affects 1 product.


Products: Redhat Slapi-Nis.

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

Upgrade to a fixed version.

## Is CVE-2015-0283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-0283 is a high-severity denial of service vulnerability in n/a, published on 30 Mar 2015. 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-2015-0283 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-0283/ (Markdown: https://insights.sbomify.com/CVE-2015-0283/index.md)
```

## Sources

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

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