# CVE-2015-5185: Null dereference in n/a

> Remote attackers can crash the SBLIM SFCB service by sending a packet with an empty className, causing a denial of service.

- **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:** 28 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h74p-5crf-72xc, SUSE-SU-2015:2116-1, SUSE-SU-2015:2218-1

## What is CVE-2015-5185?

CVE-2015-5185 is a medium-severity vulnerability in Opensuse Opensuse, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The lookupProviders function in providerMgr.c in sblim-sfcb 1.3.4 and 1.3.18 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an empty className in a packet.

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sblim-sfcb` | SUSE:Linux Enterprise Desktop 11 SP3 | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Desktop 12 | All versions | 1.4.8-5.3.3 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server 11 SP3 | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server 12 | All versions | 1.4.8-5.3.3 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server for SAP Applications 11 SP3 | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.3.11-0.25.4 |
| `sblim-sfcb` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 1.4.8-5.3.3 |

Products: Opensuse Opensuse, Standards Based Linux Instrumentation Sblim-Sfcb.

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

Apply the vendor's patch.

## Is CVE-2015-5185 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2015-5957](https://insights.sbomify.com/CVE-2015-5957/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0491](https://insights.sbomify.com/CVE-2015-0491/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2388](https://insights.sbomify.com/CVE-2008-2388/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-1866](https://insights.sbomify.com/CVE-2010-1866/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-0492](https://insights.sbomify.com/CVE-2015-0492/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5185 is a medium-severity vulnerability in Opensuse Opensuse, published on 28 Sep 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-5185 in the wild and no public exploit code.

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

## Sources

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

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