2021-11-01

SQL Server Ownership Chaining

說明
後續驗證與補充
參考資料
相關連結

筆記 SQL Server Ownership Chaining 的原理以及應用，並說明如何確認 SQL Server Objects Ownership。

說明

Ownership Chaining 是指當 Stored Procedures Object 的 Ownership 與 Table Object 的 Ownership 相同時（例如 Ownership 都是 dbo），對於沒有 Select 資料表權限的 User 而言，仍可以透過 Stored Procedures 來完成 Select。

CREATE USER U1 WITHOUT LOGIN
CREATE TABLE T1
  (
      C1 INT,
      C2 INT
  )

Insert T1 VALUES(1, 1)
GO

CREATE OR ALTER proc SP
AS
  SELECT C1 FROM T1

GRANT EXEC ON SP TO U1
EXEC('SELECT User;Exec SP') AS USER = 'U1'
EXEC('SELECT User,* FROM T1') AS USER = 'U1' -- Permission Deny

一般而言 Ownership 都會是 dbo，除非刻意將 Table Ownership 進行設定，這樣就會打破 Ownership Chaining。

CREATE USER U2 WITHOUT LOGIN
ALTER Authorization on T1 TO U2

EXEC('SELECT User;Exec SP') AS USER = 'U1'

EXEC('GRANT SELECT ON T1 TO U1') AS USER = 'U2'

EXEC('SELECT USER; EXEC SP') AS USER = 'U1'
EXEC('SELECT USER,* FROM T1') AS USER = 'U1'

確認 Schemas, Table Ownership

-- Check Schemas Ownership
SELECT S.name AS schema_name,USER_NAME(S.principal_id) AS owner_name
FROM sys.schemas AS S

-- Check Table Ownership
SELECT T.name AS table_name,
USER_NAME(T.principal_id) AS owner_name,
SCHEMA_NAME(T.schema_id) AS schema_name
FROM sys.tables AS T

確認 Logins, Users 的 Script

SELECT * FROM sys.syslogins
SELECT * FROM sys.sysusers
SELECT User, SUSER_SNAME(), DB_NAME()

應用 Ownership Chaining

左圖為 Ownership Chaining；右圖為 Ownership Chaining Broken

藉由 Ownership Chaining 能夠嚴謹的結合資料庫與應用程式開發設計，讓開發者遵循一致的程式設計模式，形成嚴謹的資料存取架構。其原則在於任何應用程式對於資料庫的存取，都是透過 Stored Procedures 來完成。

後續驗證與補充

Setup

DROP TABLE IF EXISTS dbo.T1
DROP TABLE IF EXISTS U3.T1
DROP SCHEMA IF EXISTS U3
DROP USER IF EXISTS U1
DROP USER IF EXISTS U2
DROP USER IF EXISTS U3
DROP PROC IF EXISTS SP
DROP PROC IF EXISTS SP2

CREATE TABLE T1
  (
      C1 INT,
      C2 INT
  )

Insert T1 VALUES(1, 1)
CREATE USER U1 WITHOUT LOGIN
GO

CREATE OR ALTER proc SP
AS
  SELECT C1 FROM T1
GO
GRANT EXEC ON SP TO U1
EXEC('SELECT User;Exec SP') AS USER = 'U1'

EXEC('SELECT User,* FROM T1') AS USER = 'U1'

Msg 229, Level 14, State 5, Line 53
The SELECT permission was denied on the object 'T1', 
database 'MarketDev', schema 'dbo'.

EXEC sp_table_privileges 'T1'

Change Table Authorization

CREATE USER U2 WITHOUT LOGIN
ALTER Authorization on T1 TO U2
EXEC('SELECT User;Exec SP') AS USER = 'U1'

Msg 229, Level 14, State 5, Procedure SP, Line 3 [Batch Start Line 58]
The SELECT permission was denied on the object 'T1', 
database 'MarketDev', schema 'dbo'.

ALTER Authorization on T1 TO dbo
EXEC('SELECT User;Exec SP') AS USER = 'U1'

It works again.

CREATE SCHEMA U3
CREATE USER U3 WITHOUT LOGIN
ALTER AUTHORIZATION ON SCHEMA::[U3] TO [U3]

Change Table Schema

ALTER SCHEMA U3 TRANSFER dbo.T1;

EXEC('SELECT User;Exec SP') AS USER = 'U1'

Msg 208, Level 16, State 1, Procedure SP, Line 3 [Batch Start Line 71]
Invalid object name 'dbo.T1'.

CREATE OR ALTER proc SP2
AS
  SELECT C1 FROM U3.T1
GO
GRANT EXEC ON SP2 TO U1
EXEC('SELECT User;Exec SP2') AS USER = 'U1'

Even schema is not dbo, Ownership Chaning still works.

EXEC sp_table_privileges 'T1'

Grant Permissions to dbo After Authorization by U2

GRANT SELECT ON T1 TO dbo

Cannot grant, deny, or revoke permissions to sa, dbo, 
entity owner, information_schema, sys, or yourself.

結論：真正會打破 Ownership Chaining 的是 GRANTEE，Table Owner 與 Schema 是不是 dbo 並不重要，重要的是 GRANTEE 是不是 dbo。

如果是的話，User 只要有 EXEC 對於 StoredProcedures 的權限，StoredProcedures 下面所需的關聯物件如果 GRANTEE 為 dbo 則可以正常使用。

驗證：

SCHEMA: Weired
SCHEMA Owner: Weired1
StoredProcedure: SP_W
SP_W Owner: Weired2
U1 with Execute to SP_W

CREATE USER Weired1 WITHOUT LOGIN
CREATE SCHEMA Weired
ALTER AUTHORIZATION ON SCHEMA::[Weired] TO [Weired1]

CREATE TABLE Weired.T2
  (
      C1 INT,
      C2 INT
  )
Insert Weired.T2 VALUES(1, 1)
GO

此時 T2 的 GRANTEE 是屬於 Weired1

CREATE PROC SP_W
AS
	SELECT * FROM Weired.T2
GO
GRANT EXEC ON SP_W TO U1
EXEC('SELECT User;Exec SP_W') AS USER = 'U1'

U1 執行 SP_W 會因權限不足而失敗

Msg 229, Level 14, State 5, Procedure SP_W, Line 3 [Batch Start Line 114]
The SELECT permission was denied on the object 'T2', 
database 'MarketDev', schema 'Weired'.

將 T2 的 GRANTEE 授權給 dbo

ALTER Authorization on Weired.T2 TO dbo
EXEC sp_table_privileges 'T2'

EXEC('SELECT User;Exec SP_W') AS USER = 'U1'

這次就可以順利查到結果囉，結論重點是 StoredProcedures 所使用到的物件之 GRANTEE 是否屬於 dbo，如果不是問題可大。而這個原因是來自於 SCHEMA Owner 不是 dbo，因此最好將 SCHEMA Owner 都保持在 dbo 上，除非這個 SCHEMA 有強烈的排他使用性，刻意要打破 Owership Chaining。

參考資料

Understanding SQL Server Ownership Chaining

說明