Hacking Articles Tips Tricks Videos Tutorials
471 subscribers
65.9K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
Hacking Articles Tips Tricks Videos Tutorials
Photo
KitPloit - PenTest Tools!
SQLRecon - A C# MS SQL Toolkit Designed For Offensive Reconnaissance And Post-Exploitation

https://blogger.googleusercontent.com/img/a/AVvXsEhrGrWW8kNN6b73PY-V4UuwanRsL3DIQOEcSjL-FXTamkol_FyEU4rda91UtEhbuxGglFIeZw3jWd4FLjcVfdHLzXZajG0KjvYo9mjXLj_AAoe2LJY692kxzAIj28RP6DXekH64EA6XipBVcTiIp1w1g9JguUERZdRh4rWbr5cSqpc5Oz7jHkUpYsqi=w640-h308 A C# MS-SQL toolkit designed for offensive reconnaissance and post-exploitation. For detailed usage information on each technique, refer to the wiki. UsageYou can grab a copy of SQLRecon from the releases page. Alternatively, feel free to compile the solution yourself This should be as straight forward as cloning the repo, double clicking the solution file and building. Mandatory ArgumentsThe mandatory arguments consist of an authentication type (either Windows, Local or Azure), connection parameters and a module.

* -a- Authentication Type
* -a Windows- Use Windows authentication. This uses the current users token.
* -a Local- Use local authentication. This requires the credentials for a local database user.
* -a Azure- Use Azure AD domain username and password authentication. This requires the credentials for a domain user.
If the authentication type is Windows, then you will need to supply the following parameters.

* -s SERVERNAME- SQL server hostname
* -d DATABASE- SQL server database name
* -m MODULE- The module you want to use

If the authentication type is Local, then you will need to supply the following parameters.

* -d DATABASE- SQL server database name
* -u USERNAME- Username of local SQL user
* -p PASSWORD- Password of local SQL user
* -m MODULE- The module you want to use

If the authentication type is Azure, then you will need to supply the following parameters.

* -d DATABASE- SQL server database name
* -r DOMAIN.COM- FQDN of Domain
* -u USERNAME- Username of domain user
* -p PASSWORD- Password of domain user
* -m MODULE- The module you want to use Standard ModulesStandard modules are used to interact against a single MS SQL server.

* query -o QUERY- Execute an arbitrary SQL query
* whoami- See what user you are logged in as
* mapped- See what user you are mapped to
* roles- Enumerate if the user has public and/or sysadmin roles mapped
* databases- Show all databases present on the SQL server
* tables- Show all tables in the database you are connected to
* search -o KEYWORD- Search column names within tables of the database you are connected to.
* smb -o SHARE- Capture NetNTLMv2 hash
* enablexp- Enable xp_cmdshell (requires sysadmin role or similar)
* disablexp- Disable xp_cmdshell (requires sysadmin role or similar)
* xpcmd -o COMMAND- Execute an arbitrary system command (requires sysadmin role or similar)
* enableole- Enable OLE Automation Procedures (requires sysadmin role or similar)
* disableole- Disable OLE Automation Procedures (requires sysadmin role or similar)
* olecmd -o COMMAND- Execute an arbitrary system command (requires sysadmin role or similar)
* enableclr- Enable Custom CLR Assemblies (requires sysadmin role or similar)
* disableclr- Disable Custom CLR Assemblies (requires sysadmin role or similar)
* impersonate- Enumerate any user accounts that can be impersonated
* links- Enumerate any linked SQL servers Impersonation ModulesImpersonation modules are used to interact against a single MS SQL server, under the context of an impersonated SQL user.

* iquery -i IMPERSONATEUSER -o QUERY- Execute an arbitrary SQL query as an impersonated user
* ienablexp -i IMPERSONATEUSER- Enable xp_cmd[...]
Hacking Articles Tips Tricks Videos Tutorials
KitPloit - PenTest Tools! SQLRecon - A C# MS SQL Toolkit Designed For Offensive Reconnaissance And Post-Exploitation https://blogger.googleusercontent.com/img/a/AVvXsEhrGrWW8kNN6b73PY-V4UuwanRsL3DIQOEcSjL-FXTamkol_FyEU4rda91UtEhbuxGglFIeZw3jWd4FLjcVfdHLz…
shell (requires sysadmin role or similar)
* idisablexp -i IMPERSONATEUSER- Disable xp_cmdshell (requires sysadmin role or similar)
* ixpcmd -i IMPERSONATEUSER -o COMMAND- Execute an arbitrary system command (requires sysadmin role or similar)
* ienableole -i IMPERSONATEUSER- Enable OLE Automation Procedures (requires sysadmin role or similar)
* idisableole -i IMPERSONATEUSER- Disable OLE Automation Procedures (requires sysadmin role or similar)
* iolecmd -i IMPERSONATEUSER -o COMMAND- Execute an arbitrary system command (requires sysadmin role or similar) Linked SQL Server ModulesLinked SQL Server modules are effective when you are able to interact with a linked SQL server via an established connection.

* ldatabases-l LINKEDSERVERNAME - Show all databases present on the Linked SQL server
* ltables-l LINKEDSERVERNAME - Show all tables in the database you are connected to on the Linked SQL server
* lquery-l LINKEDSERVERNAME -o QUERY - Execute an arbitrary SQL query on a linked SQL server ExamplesSee the wiki. for detailed examples. RoadmapThe below techniques are on the roadmap for future releases

* Command Execution: Custom Extended Stored Procedures Reference 1, Reference 2
* Command Execution: Custom CLR Assemblies Reference 1
* Command Execution: Agent Jobs Reference 1
* [MAYBE] Persistence Methods Reference 1 Download SQLRecon
SQLRecon - A C# MS SQL Toolkit Designed For Offensive Reconnaissance And Post-Exploitation
http://www.kitploit.com/2022/02/sqlrecon-c-ms-sql-toolkit-designed-for.html
A C# MS-SQL toolkit designed for offensive reconnaissance (https://www.kitploit.com/search/label/Reconnaissance) and post-exploitation. For detailed usage information on each technique, refer to the wiki (https://github.com/skahwah/SQLRecon/wiki). Usage You can grab a copy of SQLRecon from the releases (https://github.com/skahwah/SQLRecon/releases) page. Alternatively, feel free to compile the solution yourself This should be as straight forward as cloning the repo, double clicking the solution file and building.
Mandatory Arguments The mandatory arguments consist of an authentication type (either Windows, Local or Azure), connection parameters and a module. -a - Authentication (https://www.kitploit.com/search/label/Authentication) Type -a Windows - Use Windows authentication. This uses the current users token. -a Local - Use local authentication. This requires the credentials (https://www.kitploit.com/search/label/Credentials) for a local database user. -a Azure - Use Azure AD domain username and password authentication. This requires the credentials for a domain user. If the authentication type is Windows, then you will need to supply the following parameters. -s SERVERNAME - SQL server hostname -d DATABASE - SQL server database name -m MODULE - The module you want to use If the authentication type is Local, then you will need to supply the following parameters. -d DATABASE - SQL server database name -u USERNAME - Username of local SQL user -p PASSWORD - Password of local SQL user -m MODULE - The module you want to use If the authentication type is Azure, then you will need to supply the following parameters. -d DATABASE - SQL server database name -r DOMAIN.COM - FQDN of Domain -u USERNAME - Username of domain user -p PASSWORD - Password of domain user -m MODULE - The module you want to use Standard Modules Standard modules are used to interact against a single MS SQL server. query -o QUERY - Execute an arbitrary SQL query whoami - See what user you are logged in as mapped - See what user you are mapped to roles - Enumerate if the user has public and/or sysadmin roles mapped databases - Show all databases present on the SQL server tables - Show all tables in the database you are connected to search -o KEYWORD - Search column names within tables of the database you are connected to. smb -o SHARE - Capture NetNTLMv2 hash enablexp - Enable xp_cmdshell (requires sysadmin role or similar) disablexp - Disable xp_cmdshell (requires sysadmin role or similar) xpcmd -o COMMAND - Execute an arbitrary system command (requires sysadmin role or similar) enableole - Enable OLE Automation (https://www.kitploit.com/search/label/Automation) Procedures (requires sysadmin role or similar) disableole - Disable OLE Automation Procedures (requires sysadmin role or similar) olecmd -o COMMAND - Execute an arbitrary system command (requires sysadmin role or similar) enableclr - Enable Custom CLR Assemblies (https://www.kitploit.com/search/label/Assemblies) (requires sysadmin role or similar) disableclr - Disable Custom CLR Assemblies (requires sysadmin role or similar) impersonate - Enumerate any user accounts that can be impersonated links - Enumerate any linked SQL servers Impersonation Modules Impersonation modules are used to interact against a single MS SQL server, under the context of an impersonated SQL user. iquery -i IMPERSONATEUSER -o QUERY - Execute an arbitrary SQL query as an impersonated user ienablexp -i IMPERSONATEUSER - Enable xp_cmdshell (requires sysadmin role or similar) idisablexp -i IMPERSONATEUSER- Disable xp_cmdshell (requires sysadmin role or similar) ixpcmd -i IMPERSONATEUSER -o COMMAND - Execute an arbitrary system command (requires sysadmin role or similar) ienableole -i IMPERSONATEUSER - Enable OLE Automation Procedures (requires sysadmin role or similar) idisableole -i IMPERSONATEUSER - Disable OLE Automation Procedures (requires sysadmin
role or similar) iolecmd -i IMPERSONATEUSER -o COMMAND - Execute an arbitrary system command (requires sysadmin role or similar) Linked SQL Server Modules Linked SQL Server modules are effective when you are able to interact with a linked SQL server via an established connection. ldatabases -l LINKEDSERVERNAME - Show all databases present on the Linked SQL server ltables -l LINKEDSERVERNAME - Show all tables in the database you are connected to on the Linked SQL server lquery -l LINKEDSERVERNAME -o QUERY - Execute an arbitrary SQL query on a linked SQL server Examples See the wiki (https://github.com/skahwah/SQLRecon/wiki). for detailed examples. Roadmap The below techniques are on the roadmap for future releases Command Execution: Custom Extended Stored Procedures Reference 1 (https://stackoverflow.com/questions/12749210/how-to-create-a-simple-dll-for-a-custom-sql-server-extended-stored-procedure), Reference 2 (https://raw.githubusercontent.com/nullbind/Powershellery/master/Stable-ish/MSSQL/xp_evil_template.cpp) Command Execution: Custom CLR Assemblies Reference 1 (https://www.netspi.com/blog/technical/adversary-simulation/attacking-sql-server-clr-assemblies/) Command Execution: Agent Jobs Reference 1 (https://github.com/SofianeHamlaoui/Pentest-Notes/blob/master/Security_cheatsheets/databases/sqlserver/3-command-execution.md#agent-jobs-cmdexec-powershell-activex-etc) [MAYBE] Persistence Methods Reference 1 (https://github.com/SofianeHamlaoui/Pentest-Notes/blob/master/Security_cheatsheets/databases/sqlserver/6-persistence.md#startup-stored-procedures)

Download SQLRecon (https://github.com/skahwah/SQLRecon)
Hacking Articles Tips Tricks Videos Tutorials
Photo
Dark Reading: Attacks/Breaches
Expert Insights: Training the Data Elephant in the AI Room

Be aware of the risk of inadvertent data exposure in machine learning systems.
hacking: security in practice
How unsafe are encrypted secrets?

Recently I'm noticing rise of tools like Ansible Vault or Mozilla SOPS, git secrets etc. which allows you to manage and store your secrets encrypted in e.g. git.

My question is how safe is it to store them in public git repo vs in private vs keep them locked in a safe. Second question would be how motivated are people to go and crack random secrets on github/gitlab/...?

I know possibly everything on internet can be hacked/cracked, but I just want to know how dangerous it is for "normal" people

submitted by /u/alulord
[link] [comments]