CVE-2002-2017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsastcpd 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencesastcpd daemon in SAS/Base 8.0 allows local privilege escalation by executing arbitrary programs specified in the authprog environment variable. A local attacker can set this variable to point to a malicious program, which sastcpd will then execute with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.0= 8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if SAS Base 8.0 is installedCheck the installed version of SAS Base on the system using SAS installation tools or system inventory commandsAffected if SAS Base version equals exactly 8.0
-
Identify if SAS Integration Technologies 8.0 is installedCheck the installed version of SAS Integration Technologies using SAS installation tools or system inventory commandsAffected if SAS Integration Technologies version equals exactly 8.0
-
Locate the sastcpd daemon executableSearch for the sastcpd binary on the system - typically found in the SAS binaries or server directoryAffected if The sastcpd executable exists on the system and is accessible to the current user context
-
Check if sastcpd runs with elevated privilegesInspect the file permissions and ownership of the sastcpd executable, and check if it runs as a privileged user (root or administrator)Affected if sastcpd runs with root or administrator privileges and is executable by the current user or a privileged group the user belongs to
-
Verify the authprog environment variable is not sanitizedAttempt to set the authprog environment variable before invoking sastcpd, or inspect how sastcpd handles environment variables during executionAffected if sastcpd accepts and acts on the authprog environment variable without validation, allowing arbitrary program execution
A system is affected if it runs SAS Base 8.0 or SAS Integration Technologies 8.0 with the sastcpd daemon executable and the authprog environment variable can be controlled by a local user to trigger arbitrary program execution with elevated privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict execution permissions on sastcpd to authorized administrators only and sanitize or block the authprog environment variable before daemon execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-2017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data