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

> An attacker can cause a denial of service via a NULL pointer dereference in LibSass, affecting applications using this library.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** AZL-27684, DEBIAN-CVE-2018-11694, GHSA-352r-pm46-cmhx, UBUNTU-CVE-2018-11694

## What is CVE-2018-11694?

CVE-2018-11694 is a high-severity vulnerability in n/a, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in LibSass through 3.5.4. A NULL pointer dereference was found in the function Sass::Functions::selector_append which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Sass-Lang Libsass.

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

Upgrade to a fixed version.

## Is CVE-2018-11694 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11499](https://insights.sbomify.com/CVE-2018-11499/): Use after free in n/a (critical 9.8)
- [CVE-2022-26592](https://insights.sbomify.com/CVE-2022-26592/): Memory corruption in n/a (high 8.8)
- [CVE-2018-19827](https://insights.sbomify.com/CVE-2018-19827/): Use after free in n/a (high 8.8)
- [CVE-2018-11695](https://insights.sbomify.com/CVE-2018-11695/): Null dereference in n/a (high 8.8)
- [CVE-2018-11696](https://insights.sbomify.com/CVE-2018-11696/): Null dereference in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11694 is a high-severity vulnerability in n/a, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-11694 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-11694/ (Markdown: https://insights.sbomify.com/CVE-2018-11694/index.md)
```

## Sources

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

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