# CVE-2002-2018: Privilege escalation in n/a

> Local attackers can escalate privileges by manipulating the netencralg environment variable to trigger a segmentation fault in SAS/Base.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/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:** 14 Jul 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cqh8-v9mm-8fcx

## What is CVE-2002-2018?

CVE-2002-2018 is a high-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

sastcpd in SAS/Base 8.0 might allow local users to gain privileges by setting the netencralg environment variable, which causes a segmentation fault.

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

It affects 2 products.


Products: Sas Base, Sas Integration Technologies.

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

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

## Is CVE-2002-2018 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2017](https://insights.sbomify.com/CVE-2002-2017/): sastcpd in SAS/Base 8.0 allows local users to execute arbitrary code by setting the authprog environment variable to reference a malicious p (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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