Security readout for executives and security teams
Plain-English summary
CVE-2024-48733 reports SQL injection in a SAS Studio 9.4 SQL execution endpoint. The business risk is unauthorized or excessive data access if a low-privileged authenticated user can run SQL beyond intended scope. The vendor reportedly disputes the finding because authorized users are allowed to execute SQL statements.
Executive priority
Prioritize verification over emergency response. The CVSS score is high, but exploitation is not confirmed and the vendor disputes the issue. Focus on whether SAS Studio users can access sensitive data beyond business need.
Technical view
The CVE describes POST-body SQL command execution through /SASStudio/sasexec/sessions/{sessionID}/sql in SAS Studio 9.4, rated CVSS 8.8 with low privileges required and no user interaction. Evidence is complicated by the vendor dispute and incomplete affected-product metadata in the CVE record.
Likely exposure
Exposure is most relevant to organizations running SAS Studio 9.4 where authenticated users can reach the SAS Studio SQL endpoint. The CVE record does not provide CPEs, precise vulnerable builds, or deployment conditions.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Treat this as a disputed, high-severity authenticated data-access issue until SAS guidance and local authorization boundaries are reviewed.
Researcher notes
The key uncertainty is whether reported behavior violates an intended trust boundary. Validate authorization, data-scope enforcement, and auditability rather than assuming all SQL execution is exploitable. No patch or concrete vendor remediation is provided in the source bundle.
Mitigation direction
- Check current SAS guidance for CVE-2024-48733 and SAS Studio 9.4.
- Restrict SAS Studio access to trusted authenticated users only.
- Enforce least-privilege permissions on SAS libraries and connected data sources.
- Review authorization around SQL execution and session creation.
- Monitor for unusual SQL activity from SAS Studio sessions.
Validation and detection
- Inventory SAS Studio deployments and identify any 9.4 instances.
- Confirm whether the referenced endpoint is reachable to non-administrative users.
- Review SAS Studio user roles and database permissions.
- Check logs for unexpected SQL activity through SAS Studio sessions.
- Document vendor dispute status and any SAS advisory findings.
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.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-48733 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ACN-CVEs/CVE-2024-48733/blob/ea2da31c3d6e0140edd6a1455e6157b8ba2f7a67/SQL%20injection.pdfCVE reference, mitre
- https://support.sas.com/resources/papers/proceedings18/2387-2018.pdfCVE reference, mitre
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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.