Hacking Different methods for Database hacking

xanix

Advanced
Joined
20.10.20
Messages
112
Reaction score
782
Points
93
Database Hacking

Database contains mission critical data of the corporate firm, which makes it an obvious target by hackers.

Password guessing – Once the hacker gains control of web server, he looks for the application configuration files which typically contain the database server name, userid and password to access it. If the file is encrypted or if the information is hard-coded in the code for security reasons, hacker is left with an option to guess the password. It is found to be a common thing to leave the database system administrators account name unchanged, which solves half of hackers’ problem. In most cases the username and password are kept the same, if not, hacker can use guess work, or brute force method to gain access to the database. Depending upon the access level granted to the user, hacker gains control and is capable of doing further damage.

Packet sniffing – Modern hackers gain control of the network in which the database server is hosted, and deploy a sniffer to capture packets flowing to and from the database server. These packets are then analyzed to decipher username and password combinations and the real target is to get this information for root database administrator.

Query string manipulation – When a web server gets a request from a browser, it receives it in the form of a web url containing a query string parameter which directs the web application to database to fetch the requested data. If the application developer is not security aware, and not following best coding practices, this simple method of fetching data can lead to opening up loopholes. For example, if a list of doctors is being asked for on an insurance website, the code must ensure that a blank value in the zip code field should not be allowed. Doing so, the hacker can run a query and fetch entire data which he may not have access to, in ideal scenario.

Privilege elevation – As mentioned earlier, database servers use roles and rules to control access of a user to a particular database or a table or resource in general. An attacker usually inject scripts which try to find out most generous level of privileges and upon finding one, uses it to create further damage. Few FOSS database servers such as MangoDB, were found to be victim of these bugs which were eventually fixed.

Vulnerability exploitation – Like operating systems, even the database servers do have bugs resulting into serious vulnerabilities. Attackers can explore and exploit those either through the web layer, or by injecting a Trojan in the system dedicated for this purpose. Hackers are always looking for unpatched database system for this purpose.

SQL Injection – This attack is not a pure database attack, but in fact a combination of database and web vulnerability. It’s a very well known type, in which an attacker uses webpages to plant the attack. It is done by including parts of SQL query statements in the web form, which is usually to be filled up by web user with relevant information. If the web page is not capable of handling this situation in a secure manner, it ends up sending this bogus request to the database. The attacker can simply run a select query to dump the entire database on his machine by this method, which makes it a favorite of hackers and hence dangerous from firm’s security standpoint.

Database DoS – As a typical denial of service attack, the attacker plants a code either on the web server or the database server itself, which sends requests to the database in order to overwhelm it. For example, the queries can be either at application layer to dump database contents in a loop, or at TCP layer, it can be a SYN packet storm. The end result is, the database gives up at one point and stops responding to the queries, thus resulting into a complete website or application failure.
 

Beast2274

Newbie
Joined
24.07.23
Messages
10
Reaction score
4
Points
1
Database Hacking

Database contains mission critical data of the corporate firm, which makes it an obvious target by hackers.

Password guessing – Once the hacker gains control of web server, he looks for the application configuration files which typically contain the database server name, userid and password to access it. If the file is encrypted or if the information is hard-coded in the code for security reasons, hacker is left with an option to guess the password. It is found to be a common thing to leave the database system administrators account name unchanged, which solves half of hackers’ problem. In most cases the username and password are kept the same, if not, hacker can use guess work, or brute force method to gain access to the database. Depending upon the access level granted to the user, hacker gains control and is capable of doing further damage.

Packet sniffing – Modern hackers gain control of the network in which the database server is hosted, and deploy a sniffer to capture packets flowing to and from the database server. These packets are then analyzed to decipher username and password combinations and the real target is to get this information for root database administrator.

Query string manipulation – When a web server gets a request from a browser, it receives it in the form of a web url containing a query string parameter which directs the web application to database to fetch the requested data. If the application developer is not security aware, and not following best coding practices, this simple method of fetching data can lead to opening up loopholes. For example, if a list of doctors is being asked for on an insurance website, the code must ensure that a blank value in the zip code field should not be allowed. Doing so, the hacker can run a query and fetch entire data which he may not have access to, in ideal scenario.

Privilege elevation – As mentioned earlier, database servers use roles and rules to control access of a user to a particular database or a table or resource in general. An attacker usually inject scripts which try to find out most generous level of privileges and upon finding one, uses it to create further damage. Few FOSS database servers such as MangoDB, were found to be victim of these bugs which were eventually fixed.

Vulnerability exploitation – Like operating systems, even the database servers do have bugs resulting into serious vulnerabilities. Attackers can explore and exploit those either through the web layer, or by injecting a Trojan in the system dedicated for this purpose. Hackers are always looking for unpatched database system for this purpose.

SQL Injection – This attack is not a pure database attack, but in fact a combination of database and web vulnerability. It’s a very well known type, in which an attacker uses webpages to plant the attack. It is done by including parts of SQL query statements in the web form, which is usually to be filled up by web user with relevant information. If the web page is not capable of handling this situation in a secure manner, it ends up sending this bogus request to the database. The attacker can simply run a select query to dump the entire database on his machine by this method, which makes it a favorite of hackers and hence dangerous from firm’s security standpoint.

Database DoS – As a typical denial of service attack, the attacker plants a code either on the web server or the database server itself, which sends requests to the database in order to overwhelm it. For example, the queries can be either at application layer to dump database contents in a loop, or at TCP layer, it can be a SYN packet storm. The end result is, the database gives up at one point and stops responding to the queries, thus resulting into a complete website or application failure.
hmmm
 

SKYJAY

Newbie
Joined
31.07.23
Messages
9
Reaction score
1
Points
3
數據庫黑客

數據庫包含企業公司的關鍵任務數據,這使其成為黑客的明顯目標。

密碼猜測 – 一旦黑客獲得了 Web 服務器的控制權,他就會尋找應用程序配置文件,其中通常包含數據庫服務器名稱、用戶 ID 和密碼來訪問它。如果文件已加密或者出於安全原因將信息硬編碼在代碼中,則黑客可以選擇猜測密碼。發現數據庫系統管理員賬戶名不變是很常見的事情,這樣就解決了一半的黑客問題。在大多數情況下,用戶名和密碼保持相同,如果不同,黑客可以使用猜測或暴力方法來獲取對數據庫的訪問權限。根據授予用戶的訪問級別,黑客獲得控制權並能夠造成進一步的損害。

數據包嗅探—— 現代黑客控制了數據庫服務器所在的網絡,並部署嗅探器來捕獲流向和來自數據庫服務器的數據包。然後分析這些數據包以破譯用戶名和密碼組合,真正的目標是為根數據庫管理員獲取此信息。

查詢字符串操作 – 當 Web 服務器從瀏覽器獲取請求時,它以包含查詢字符串參數的 Web URL 形式接收該請求,該參數將 Web 應用程序定向到數據庫以獲取請求的數據。如果應用程序開發人員沒有安全意識,並且不遵循最佳編碼實踐,這種簡單的獲取數據的方法可能會導致出現漏洞。例如,如果在保險網站上要求提供醫生列表,則代碼必須確保郵政編碼字段中不允許出現空白值。這樣做,在理想情況下,黑客可以運行查詢並獲取他可能無法訪問的整個數據。

權限提升 –如前所述,數據庫服務器通常使用角色和規則來控制用戶對特定數據庫、表或資源的訪問。攻擊者通常會注入腳本,嘗試找出最慷慨的特權級別,並在找到後使用它來造成進一步的損害。很少有 FOSS 數據庫服務器(例如 MangoDB)被發現是這些錯誤的受害者,但這些錯誤最終得到了修復。

漏洞利用——與操作系統一樣,即使是數據庫服務器也存在導致嚴重漏洞的錯誤。攻擊者可以通過 Web 層或通過在專用於此目的的系統中註入木馬來探索和利用這些內容。為此,黑客總是尋找未打補丁的數據庫系統。

SQL注入—— 這種攻擊不是純粹的數據庫攻擊,而是數據庫和Web漏洞的結合。這是一種眾所周知的類型,攻擊者使用網頁來發起攻擊。它是通過在 Web 表單中包含部分 SQL 查詢語句來完成的,通常由 Web 用戶填寫相關信息。如果網頁無法以安全的方式處理這種情況,它最終會將此虛假請求發送到數據庫。攻擊者可以簡單地運行一個選擇查詢,通過這種方法將整個數據庫轉儲到他的機器上,這使得它成為黑客的最愛,因此從公司的安全角度來看是危險的。

數據庫 DoS – 作為一種典型的拒絕服務攻擊,攻擊者在 Web 服務器或數據庫服務器本身上植入代碼,向數據庫發送請求以淹沒數據庫。例如,查詢可以在應用程序層循環轉儲數據庫內容,也可以在 TCP 層,它可以是 SYN 數據包風暴。最終結果是,數據庫在某一時刻放棄並停止響應查詢,從而導致網站或應用程序完全失敗。
好的
 
Top Bottom