CVE-2024-48735: Directory Traversal in /SASStudio/sasexec/sessions/{sessionID}/workspace/{InternalPath} in SAS Studio 9.4 a...
Directory Traversal in /SASStudio/sasexec/sessions/{sessionID}/workspace/{InternalPath} in SAS Studio 9.4 allows remote attacker to access internal files by manipulating default path during file download. NOTE: this is disputed by the vendor because these filesystem paths are allowed for authorized users.
Security readout for executives and security teams
Plain-English summary
CVE-2024-48735 describes a disputed directory traversal issue in SAS Studio 9.4. The report says an authenticated remote user could manipulate a workspace file download path to read internal files. SAS disputes this as intended access for authorized users, so urgency depends on how your SAS Studio permissions and file access are configured.
Executive priority
Treat as a high-priority review item, not confirmed emergency response. Validate whether SAS Studio users can reach sensitive files beyond intended authorization, then follow SAS guidance if remediation is needed.
Technical view
The claimed issue is CWE-22 in /SASStudio/sasexec/sessions/{sessionID}/workspace/{InternalPath}. CVSS 3.1 is 7.7: network reachable, low privileges required, no user interaction, changed scope, high confidentiality impact, no integrity or availability impact. The CVE record notes vendor dispute because these filesystem paths are allowed for authorized users.
Likely exposure
Potentially relevant to SAS Studio 9.4 environments. The source bundle does not provide CPEs, exact maintenance levels, or affected deployment configurations. Exposure likely requires authenticated access and a valid SAS Studio session context.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. A public GitHub PDF is referenced, but the vendor dispute materially affects confidence and prioritization.
Researcher notes
Evidence is limited and disputed. Do not assume unauthenticated traversal or confirmed exploitability. Focus validation on authorization boundaries, session requirements, file access design, and whether observed access exceeds documented SAS Studio user privileges.
Mitigation direction
Check SAS vendor guidance for official status, fixes, or configuration advice.
Restrict SAS Studio access to trusted users and managed networks.
Review SAS Studio authorization and least-privilege file access policies.
Monitor logs for unusual workspace file download path activity.
Assess compensating controls where broad filesystem access is business-approved.
Validation and detection
Inventory SAS Studio 9.4 deployments and externally reachable instances.
Confirm workspace download access requires authentication and valid session context.
Review whether authorized users can access only intended filesystem paths.
Search SAS Studio logs for unexpected internal file download patterns.
Document any business-approved filesystem access that explains the behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.