Menu

Star on GitHub · 3.2k

CVE-2002-2017

10.0 · HIGH

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.

Published Dec 31, 2002sasEPSS 2.47%

Overview

CVE-2002-2017 is a high-severity vulnerability affecting sas base. It was published on December 31, 2002 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories and patches from sas. Update base to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2002-2017?

CVE-2002-2017 is a high-severity vulnerability affecting sas base. It was published on December 31, 2002 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2002-2017?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2002-2017?

Check the references section for vendor advisories and patches from sas. Update base to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2002-2017?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2002-2017 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2002

View all