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
Published
Updated
Check this codebase for CVE-2002-2017 and fix it if it is affected.
What it is: CVE-2002-2017 is a critical vulnerability in n/a, published on 14 Jul 2005.
Exploitation: There is no known exploitation of CVE-2002-2017 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-2017/ (Markdown: https://insights.sbomify.com/CVE-2002-2017/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2002-2017?
CVE-2002-2017 is a critical vulnerability in n/a, published on 14 Jul 2005.
Official description
sastcpd in SAS/Base 8.0 allows local users to execute arbitrary code by setting the authprog environment variable to reference a malicious program, which is then executed by sastcpd.
Which versions are affected by CVE-2002-2017?
It affects 2 products.
Products include Sas Base, Sas Integration Technologies.
How do I fix CVE-2002-2017?
No fix has been published for CVE-2002-2017 yet. Limit exposure of the affected software until one is available.
Is CVE-2002-2017 being exploited?
There is no known exploitation of CVE-2002-2017 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-r986-j2xg-7944.