Security readout for executives and security teams
Plain-English summary
This is an old local privilege-escalation flaw in SAP R/3 Web Application Server Demo before 1.5. A local user could influence how saposcol finds a helper program and potentially gain root access. It is not described as remotely exploitable in the provided sources.
Executive priority
Treat as a targeted legacy-risk item. Prioritize verification if old SAP demo software remains on business-critical systems. Urgency is lower than an internet-facing remote flaw, but impact can be severe where local users or compromised accounts exist.
Technical view
saposcol trusts the PATH environment variable when locating and executing the expand program. A local user can alter PATH so saposcol runs a malicious expand program instead, leading to root-level code execution. The provided data identifies SAP R/3 Web Application Server Demo before 1.5 as affected.
Likely exposure
Likely limited to legacy SAP R/3 Web Application Server Demo installations before version 1.5. Exposure requires local user access on the affected host. Modern SAP environments may not include this demo component, but legacy system inventories should verify.
Exploitation context
The source bundle does not cite CISA KEV listing or current active exploitation. The described attack requires local access and PATH manipulation. Public exploit status is not established by the provided sources.
Researcher notes
The record is sparse: no CVSS, CWE, detailed vendor advisory, or exploit-status evidence is included. Analysis should stay anchored to local privilege escalation via PATH trust in saposcol. Validate product/version carefully because the affected CPE data is not populated.
Mitigation direction
- Identify any SAP R/3 Web Application Server Demo installations and their versions.
- Upgrade affected demo installations to version 1.5 or later if vendor guidance supports it.
- Remove unused demo components from production and sensitive systems.
- Restrict local shell access on hosts running legacy SAP components.
- Check SAP or vendor advisories for current supported remediation guidance.
Validation and detection
- Search asset inventories for SAP R/3 Web Application Server Demo before 1.5.
- Confirm whether saposcol exists on identified hosts.
- Review local user access on systems running affected components.
- Check whether PATH-dependent execution behavior is present in the installed version.
- Document compensating controls if upgrade or removal is not immediately possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2001-0366 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- linux-sap-execute-code(6487)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.