# CVE-2018-6644: Null dereference in n/a

> A null pointer dereference in SBLIM SFCB allows remote attackers to cause a denial of service via a crafted POST request.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-84x3-c759-r67j, UBUNTU-CVE-2018-6644, openSUSE-SU-2024:11368-1

## What is CVE-2018-6644?

CVE-2018-6644 is a high-severity vulnerability in n/a, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SBLIM Small Footprint CIM Broker (SFCB) 1.4.9 has a null pointer (DoS) vulnerability via a crafted POST request to the /cimom URI.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2018-6644?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sblim-sfcb` | openSUSE:Tumbleweed | All versions | 1.4.9-13.6 |

Products: Sblim Project Small Footprint Cim Broker.

## How do I fix CVE-2018-6644?

Apply the vendor's patch.

## Is CVE-2018-6644 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6644 and fix it if it is affected.

What it is: CVE-2018-6644 is a high-severity vulnerability in n/a, published on 8 Feb 2018. 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-2018-6644 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-2018-6644/ (Markdown: https://insights.sbomify.com/CVE-2018-6644/index.md)
```

## Sources

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

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