Hacking on Medium
Hacking websites: session hijacking with XSS (and how to protect your Django website)

https://cdn-images-1.medium.com/max/1200/1*XJwUkOmAmZW94SJlqIn6mg.png
One vulnerability builds on top of another: a bad actor can perform a series of attacks on your website that starts as a simple XSS attack…

Continue reading on System Weakness »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
$LSS Lossless FA Report

https://cdn-images-1.medium.com/max/1024/1*9cIYY8OL9wI9YmmTTsdZuA.jpeg
V2 Update

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
All about XSS(Part 2)

https://cdn-images-1.medium.com/max/933/1*t8DuWKRh4ERXsQS2C8me2A.png
Exploiting reflected XSS — Going beyond an Alert box

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Slowloris DDOS Attack

https://cdn-images-1.medium.com/max/808/1*YuATWDqEtN7l0zE56m_gUQ.jpeg
Who is Slow lorises? Why is it called as slowloris attack? How can I perform a denial of service attack using this ?

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Bypass Rate Limit — A blank space leads to this random encounter!

Hello All, Hope you are having a great time!Continue reading on InfoSec Write-ups »
Read more...

hacking: security in practice
Can I get caught for my hacking my teacher's account on Microsoft Teams?

Is it possible to get caught hacking my teacher's account, I know that log files are saved every time you log into a website, so hypothetically can I get caught this way?

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

___________________________
@hacking_Attack
@Hacking_Video

365Inspect - A PowerShell Script That Automates The Security Assessment Of Microsoft Office 365 Environments
http://www.kitploit.com/2022/04/365inspect-powershell-script-that.html

___________________________
@hacking_Attack
@Hacking_Video

Further the state of O365 security by authoring a PowerShell (https://www.kitploit.com/search/label/PowerShell) script that automates the security assessment of Microsoft Office 365 environments.
Setup 365Inspect requires the administrative PowerShell modules for Microsoft Online, Azure AD (We recommend installing the AzureADPreview module), Exchange administration, Microsoft Graph, Microsoft Intune, Microsoft Teams, and Sharepoint administration. The 365Inspect.ps1 PowerShell script will validate the installed modules. If you do not have these modules installed, you will be prompted to install them, and with your approval, the script will attempt installation. Otherwise, you should be able to install them with the following commands in an administrative PowerShell prompt, or by following the instructions at the references below: Install-Module -Name MSOnline

Install-Module -Name AzureADPreview

Install-Module -Name ExchangeOnlineManagement

Install-Module -Name Microsoft.Online.SharePoint.PowerShell

Install-Module -Name Microsoft.Graph

Install-Module -Name MicrosoftTeams

Install-Module -Name Microsoft.Graph.Intune
Install MSOnline PowerShell (https://docs.microsoft.com/en-us/powershell/azure/active-directory/install-msonlinev1?view=azureadps-1.0) Install Azure AD PowerShell (https://docs.microsoft.com/en-us/powershell/module/azuread/?view=azureadps-2.0) Install Exchange Online PowerShell (https://docs.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps) Install SharePoint (https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-online/connect-sharepoint-online?view=sharepoint-ps) Install Microsoft Graph SDK (https://docs.microsoft.com/en-us/graph/powershell/installation) Install Microsoft Teams PowerShell Module (https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install) Install Microsoft Intune PowerShell SDK (https://github.com/microsoft/Intune-PowerShell-SDK) Once the above are installed, download the 365Inspect source code folder from Github using your browser or by using git clone. As you will run 365Inspect with administrative privileges, you should place it in a logical location and make sure the contents of the folder are readable and writable only by the administrative user. This is especially important if you intend to install 365Inspect in a location where it will be executed frequently or used as part of an automated (https://www.kitploit.com/search/label/Automated) process. Usage To run 365Inspect, open a PowerShell console and navigate to the folder you downloaded 365Inspect into: cd 365Inspect
You will interact with 365Inspect by executing the main script file, 365Inspect.ps1, from within the PowerShell command prompt. All 365Inspect requires to inspect your O365 tenant is access via an O365 account with proper permissions, so most of the command line (https://www.kitploit.com/search/label/Command%20Line) parameters relate to the organization being assessed and the method of authentication. Execution of 365Inspect looks like this: .\365Inspect.ps1 -OrgName -OutPath -Auth
For example, to log in by entering your credentials (https://www.kitploit.com/search/label/Credentials) in a browser with MFA support: .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA
365Inspect can be run with only specified Inspector modules, or conversely, by excluding specified modules. For example, to log in by entering your credentials in a browser with MFA support: .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA -SelectedInspectors inspector1, inspector2
or .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA -ExcludedInspectors inspector1, inspector2, inspector3

___________________________
@hacking_Attack
@Hacking_Video

# to fetch these transport rules within this module; assume main 365Inspect harness has logged us in already.
$safe_attachment_bypass_rules = (Get-TransportRule | Where { $_.SetHeaderName -eq "X-MS-Exchange-Organization-SkipSafeAttachmentProcessing" }).Identity

# If some of the parsed O365 objects were found to have the security flaw this module is inspecting for,
# return a list of strings representing those objects. This is what will end up as the "Affected Objects"
# field in the report.
If ($safe_attachment_bypass_rules.Count -ne 0) {
return $safe_attachment_bypass_rules
}

# If none of the parsed O365 obj ects were found to have the security flaw this module is inspecting for,
# returning $null indicates to 365Inspect that there were no findings for this module.
return $null
}

# Return the results of invoking the inspector function.
return Inspect-BypassingSafeAttachments
Example .json file, BypassingSafeAttachments.json: Rules screen in the Exchange Admin Center. Look for the offending rules and begin the process of assessing who created them and whether they are necessary to the continued function of your organization. If they are not, remove the rules.", "AffectedObjects": "", "References": [ { "Url": "https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/manage-mail-flow-rules", "Text": "Manage Mail Flow Rules in Exchange Online" }, { "Url": "https://www.undocumented-features.com/2018/05/10/atp-safe-attachments-safe-links-and-anti-phishing-policies-or-all-the-policies-you-can-shake-a-stick-at/#Bypass_Safe_Attachments_Processing", "Text": "Undocumented Features: Safe Attachments, Safe Links, and Anti-Phishing Policies" } ] }'>{
"FindingName": "Do Not Bypass the Safe Attachments Filter",
"Description": "In Exchange, it is possible to create mail transport rules that bypass the Safe Attachments detection capability. The rules listed above bypass the Safe Attachments capability. Consider revie1wing these rules, as bypassing the Safe Attachments capability even for a subset of senders could be considered insecure depending on the context or may be an indicator of compromise.",
"Remediation": "Navigate to the Mail Flow -> Rules screen in the Exchange Admin Center. Look for the offending rules and begin the process of assessing who created them and whether they are necessary to the continued function of your organization. If they are not, remove the rules.",
"AffectedObjects": "",
"References": [
{
"Url": "https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/manage-mail-flow-rules",
"Text": "Manage Mail Flow Rules in Exch ange Online"
},
{
"Url": "https://www.undocumented-features.com/2018/05/10/atp-safe-attachments-safe-links-and-anti-phishing-policies-or-all-the-policies-you-can-shake-a-stick-at/#Bypass_Safe_Attachments_Processing",
"Text": "Undocumented Features: Safe Attachments, Safe Links, and Anti-Phishing Policies"
}
]
}
Once you drop these two files in the .\inspectors folder, they are considered part of 365Inspect's module inventory and will run the next time you execute 365Inspect. You have just created the BypassingSafeAttachments Inspector module. That's all! 365Inspect will throw a pretty loud and ugly error if something in your module doesn't work or doesn't follow 365Inspect conventions, so monitor the command line output. About Security 365Inspect is a script harness that runs other inspector script modules stored in the .\inspectors folder. As with any other script you may run with elevated privileges, you should observe certain security hygiene practices: No untrusted user should have write access to the 365Inspect folder/files, as that user could then overwrite scripts or templates therein and induce you to run malicious code. No script module should be placed in .\inspectors unless you trust the source of that script module.

___________________________
@hacking_Attack
@Hacking_Video

Download 365Inspect (https://github.com/soteria-security/365Inspect)

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
The Day the Russo-Ukrainian War Came Home

Note to the reader: If you are wondering about the spiritual side of the article you are about to read, persist. Read through the initial…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
I Got Crypto Hacked. What Should I Do?

https://cdn-images-1.medium.com/max/1000/1*D-no6c2TbJPEFPasz5BBtQ.jpeg
If you got crypto hacked, your cryptocurrency was stolen or hacked. This can happen through a variety of means, including phishing scams…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
365Inspect - A PowerShell Script That Automates The Security Assessment Of Microsoft Office 365 Environments

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieSTuGlWRVFvGM5A6p7ALc753nanyWj-aezEv87nvsZ36U1XXFwO7uMkR3HMSyTD6q4EZXme1Exy9IieMoxLhD5R07fsoWgyvn0XTG60jvfwJSZ711C43bT_AAOLW62J6B6d4hHvfVh8DpxkJ-7fbZLmx9WYkko3x9gWTV4pYHr-zAbdxTIdlxvkSI/w640-h366/365.jpg Further the state of O365 security by authoring a PowerShell script that automates the security assessment of Microsoft Office 365 environments. Setup365Inspect requires the administrative PowerShell modules for Microsoft Online, Azure AD (We recommend installing the AzureADPreview module), Exchange administration, Microsoft Graph, Microsoft Intune, Microsoft Teams, and Sharepoint administration.

The 365Inspect.ps1 PowerShell script will validate the installed modules.

If you do not have these modules installed, you will be prompted to install them, and with your approval, the script will attempt installation. Otherwise, you should be able to install them with the following commands in an administrative PowerShell prompt, or by following the instructions at the references below: Install-Module -Name MSOnline

Install-Module -Name AzureADPreview

Install-Module -Name ExchangeOnlineManagement

Install-Module -Name Microsoft.Online.SharePoint.PowerShell

Install-Module -Name Microsoft.Graph

Install-Module -Name MicrosoftTeams

Install-Module -Name Microsoft.Graph.Intune Install MSOnline PowerShell Install Azure AD PowerShell Install Exchange Online PowerShell Install SharePoint Install Microsoft Graph SDK Install Microsoft Teams PowerShell Module Install Microsoft Intune PowerShell SDK

Once the above are installed, download the 365Inspect source code folder from Github using your browser or by using git clone.

As you will run 365Inspect with administrative privileges, you should place it in a logical location and make sure the contents of the folder are readable and writable only by the administrative user. This is especially important if you intend to install 365Inspect in a location where it will be executed frequently or used as part of an automated process. UsageTo run 365Inspect, open a PowerShell console and navigate to the folder you downloaded 365Inspect into: cd 365Inspect You will interact with 365Inspect by executing the main script file, 365Inspect.ps1, from within the PowerShell command prompt.

All 365Inspect requires to inspect your O365 tenant is access via an O365 account with proper permissions, so most of the command line parameters relate to the organization being assessed and the method of authentication.

Execution of 365Inspect looks like this: .\365Inspect.ps1 -OrgName For example, to log in by entering your credentials in a browser with MFA support: .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA 365Inspect can be run with only specified Inspector modules, or conversely, by excluding specified modules.

For example, to log in by entering your credentials in a browser with MFA support: .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA -SelectedInspectors inspector1, inspector2 or .\365Inspect.ps1 -OrgName mycompany -OutPath ..\365_report -Auth MFA -ExcludedInspectors inspector1, inspector2, inspector3 To break down the parameters further:

* OrgName is the name of the core organization or "company" of your O365 instance, which will be inspected.
* If you do not know your organization name, you can navigate to the list of all Exchange domains in O365. The topmost domain should be named domain_name.onmicrosoft.com. In that example, domain_name is your organization name and should be used when executing 365Inspect.

* OutPath is the path to a folder wh[...]

___________________________
@hacking_Attack
@Hacking_Video

ere the report generated by 365Inspect will be placed.
* Auth is a selector that should be one of the literal values "MFA", "CMDLINE", or "ALREADY_AUTHED".
* Auth controls how 365Inspect will authenticate to all of the Office 365 services.
* Auth MFA will produce a graphical popup in which you can type your credentials and even enter an MFA code for MFA-enabled accounts.
* Auth ALREADY_AUTHED instructs 365Inspect not to authenticate before scanning. This may be preferable if you are executing 365Inspect from a PowerShell prompt where you already have valid sessions for all of the described services, such as one where you have already executed 365Inspect.

* SelectedInspectors is the name or names of the inspector or inspectors you wish to run with 365Inspect. If multiple inspectors are selected they must be comma separated. Only the named inspectors will be run.
* ExcludedInspectors is the name or names of the inspector or inspectors you wish to prevent from running with 365Inspect. If multiple inspectors are selected they must be comma separated. All modules other included modules will be run.

When you execute 365Inspect with -Auth MFA, it may produce several graphical login prompts that you must sequentially log into. This is normal behavior as Exchange, SharePoint etc. have separate administration modules and each requires a different login session. If you simply log in the requested number of times, 365Inspect should begin to execute. This is the opposite of fun and we're seeking a workaround, but needless to say we feel the results are worth the minute spent looking at MFA codes.

As 365Inspect executes, it will steadily print status updates indicating which inspection task is running.

365Inspect may take some time to execute. This time scales with the size and complexity of the environment under test. For example, some inspection tasks involve scanning the account configuration of all users. This may occur near-instantly for an organization with 50 users, or could take entire minutes (!) for an organization with 10000. Output365Inspect creates the directory specified in the out_path parameter. This directory is the result of the entire 365Inspect inspection. It contains three items of note:

* Report.html: graphical report that describes the O365 security issues identified by 365Inspect, lists O365 objects that are misconfigured, and provides remediation advice.
* Various text files named [Inspector-Name]: these are raw output from inspector modules and contain a list (one item per line) of misconfigured O365 objects that contain the described security flaw. For example, if a module Inspect-FictionalMFASettings were to detect all users who do not have MFA set up, the file "Inspect-FictionalMFASettings" in the report ZIP would contain one user per line who does not have MFA set up. This information is only dumped to a file in cases where more than 15 affected objects are discovered. If less than 15 affected objects are discovered, the objects are listed directly in the main HTML report body.
* Report.zip: zipped version of this entire directory, for convenient distribution of the results in cases where some inspector modules generated a large amount of findings. Necessary Privileges365Inspect can't run properly unless the O365 account you authenticate with has appropriate privileges. 365Inspect requires, at minimum, the following:

* Global Administrator
* SharePoint Administrator

We realize that these are extremely permissive roles, unfortunately due to the use of Microsoft Graph, we are restricted from using lesser prileges by Microsoft. Application and Cloud Application Administrator roles (used to grant delegated and application permissions) are restricted from granting permissions for Microsoft Graph or Azure AD PowerShell modules. https://docs.microsoft.com/en-us/azure/active-directory/roles/permissions-reference#application-administrator Developing Inspector Modules365Inspect is designed to be easy to expand, with th[...]

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
365Inspect - A PowerShell Script That Automates The Security Assessment Of Microsoft Office 365 Environments

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Mass email & texting

Anyone have a source I can get back at these telemarketing people? Also have this one number calling me all the time, and when I call back she is soooo rude. I’d love to send 1000 text messages to these people, pref about Nancy pelosi or something funny like that. A joke I guess you can call it. Any help?

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

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
Delta Controls enteliTOUCH 3.40.3935 Cookie User Password Disclosure

https://4.bp.blogspot.com/-slZrAXCcTc4/WWlvSkUdx-I/AAAAAAAAINc/GD9pE2wpupUfP-XcYlxrz5jw2m91dZTOgCLcBGAs/s1600/h39.png
Delta Controls enteliTOUCH versions 3.40.3935, 3.40.3706, and 3.33.4005 suffer from a cookie user password disclosure vulnerability.

MD5 | 9fbce69012e907edfb98cfcb3760439d

Download

Delta Controls enteliTOUCH 3.40.3935 Cookie User Password Disclosure
Vendor: Delta Controls Inc.
Product web page: https://www.deltacontrols.com
Affected version: 3.40.3935
3.40.3706
3.33.4005

Summary: enteliTOUCH - Touchscreen Building Controller. Get instant
access to the heart of your BAS. The enteliTOUCH has a 7-inch,
high-resolution display that serves as an interface to your building.
Use it as your primary interface for smaller facilities or as an
on-the-spot access point for larger systems. The intuitive,
easy-to-navigate interface gives instant access to manage your BAS.

Desc: The application suffers from a cleartext transmission/storage
of sensitive information in a Cookie. This allows a remote
attacker to intercept the HTTP Cookie authentication credentials
through a man-in-the-middle attack.

Tested on: DELTA enteliTOUCH
Vulnerability discovered by Gjoko 'LiquidWorm' Krstic
@zeroscience
Advisory ID: ZSL-2022-5704
Advisory URL: https://www.zeroscience.mk/en/vulnerabilities/ZSL-2022-5704.php
06.04.2022

--
GET /deltaweb/hmi_useredit.asp?ObjRef=BAC.1000.ZSL3&formAction=Edit HTTP/1.1
Host: 192.168.0.210
Cache-Control: max-age=0
User-Agent: Toucher/1.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Referer: http://192.168.0.210/deltaweb/hmi_userconfig.asp
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Cookie: Previous=; lastLoaded=; LastUser=DELTA; LogoutTime=10; UserInstance=1; UserName=DELTA; Password=LOGIN; LastGraphic=; LastObjRef=; AccessKey=DADGGEOFNILEJMBBCNDKFNJPHPPJDAEDGEBJACPEAPBHDCGPCAGNNDEOJIJEOPPLOEKCFMAFNHDJPHGACMDFMPFDNONPIJAHBBNAAIDMDHCCPMAJDELDNLOPBPDCKELJADDKICPMMPCNEOMBHMKIIBJHFAJKNKJFGDEOLPMGMNBEHFLNEDIFMJKMCJKBHPGGEMHJJGMOMAECDKDIIKGNDDGANIHDKPNACLMANGJAOBDNJCFGEIHIJICLPGOFFMDOOLOJCJPAPPKOJFCKFAHDDAGNLCAHKKKGHCBODHBNDCOECGHG
Connection: close

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video