Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.8K 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
Web App Pen Testing - Learning SQL Injection
https://www.reddit.com/r/Pentesting/comments/nmawn4/web_app_pen_testing_learning_sql_injection/

<!-- SC_OFF -->Hello Everyone, I'm on my journey to become a web app pen tester and I have started with the Portswigger Web Security Academy which I'm finding incredibly useful so far. I have started on the SQL injection topic and I've just started looking at blind SQL injection and its the first time where I have relied heavily on hints/solutions to assist me in completing the labs. What I'm struggling with is the many extra variables you may potentially have to include in order to be successful. So my question is how would you know whether to use URL encoding vs concatenation vs a comment trailer or even a combination of these? Is it simply trial and error or is there a set pattern you should always try when discovering a potential injectable field? Some examples below. Lab example with double concatenation encased in quotes TrackingId=xyz'||(SELECT ' ')||' Lab example with concatenation and comment trailer TrackingId=x'||pg_sleep(10)-- Lab example with some URL encoding and + TrackingId=x'%3BSELECT+CASE+WHEN+(1=1)+THEN+pg_sleep(10)+ELSE+pg_sleep(0)+END-- At the moment these labs feel impossible without these hints/walkthroughs so any advice would be greatly appreciated. Thanks in advance :) <!-- SC_ON --> submitted by /u/lewis20188 (https://www.reddit.com/user/lewis20188)
[link] (https://www.reddit.com/r/Pentesting/comments/nmawn4/web_app_pen_testing_learning_sql_injection/) [comments] (https://www.reddit.com/r/Pentesting/comments/nmawn4/web_app_pen_testing_learning_sql_injection/)
Hacking Articles Tips Tricks Videos Tutorials
Photo
Black Hat Ethical Hacking
Pulse Secure VPNs Get Quick Fix for Critical RCE

https://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Pulse Secure VPNs Get Quick Fix for Critical RCEPost Views: 160
Reading Time: 1 Minute
Pulse Secure has issued a workaround for a critical remote-code execution (RCE) vulnerability in its Pulse Connect Secure (PCS) VPNs that may allow an unauthenticated, remote attacker to execute code as a user with root privileges.
Pulse Secure’s parent company, Ivanti, issued an out-of-band advisory on May 14. The company explained that this high-severity bug – identified as CVE-2021-22908 and rated CVSS 8.5 – affects Pulse Connect Secure versions 9.0Rx and 9.1Rx.

“Buffer Overflow in Windows File Resource Profiles in 9.X allows a remote authenticated user with privileges to browse SMB shares to execute arbitrary code as the root user,” according to the advisory. “As of version 9.1R3, this permission is not enabled by default.”

The CERT Coordination Center issued a report about the vulnerability, explaining that the problem stems from a buffer overflow vulnerability in the PCS gateway. CERT/CC explained that the gateway’s ability to connect to Windows file shares through a number of CGI endpoints could be leveraged to carry out an attack.

“When specifying a long server name for some SMB operations, the smbcltapplication may crash due to either a stack buffer overflow or a heap buffer overflow, depending on how long of a server name is specified,” CERT/CC noted. PCS 9.1R11.4 systems are vulnerable: CERT/CC said that it’s  managed to trigger the vulnerability by targeting the CGI script /dana/fb/smb/wnf.cgi, although “Other CGI endpoints may also trigger the vulnerable code.”
See Also: 100M Android Users Hit By Rampant Cloud Leaks There’s currently no practical solution to this problem, at least not that CERT/CC is aware of, according to Will Dormann, who both discovered the vulnerability and wrote up the CERT/CC report. He offered two workarounds: Fix No. 1: Apply XML WorkaroundPulse Secure has published a quick fix: a Workaround-2105.xml file with a mitigation to protect against the vulnerability. “Importing this XML workaround will activate the protections immediately,” according to Dormann’s report, and “does not require any downtime for the VPN system.

The workaround blocks requests that match these URI patterns: ^/+dana/+fb/+smb^/+dana-cached/+fb/+smbDormann advised users to note that Workaround-2105.xmlwill automatically deactivate the mitigations applied by an earlier workaround, Workaround-2104.xml. That makes it “imperative that a PCS system is running 9.1R11.4 before applying the Workaround-2105.xmlmitigation,” he said, to ensure that the vulnerabilities outlined in SA44784 aren’t reintroduced as the result of applying the workaround.

The workaround will block the ability to use Windows File Share Browser.
See Also: Offensive Security Tool: Snallygaster Fix No. 2: Set a Windows File Access PolicyDormann said that a PCS system that started as 9.1R2 or earlier will retain the default Initial File Browsing Policy of Allow for \\*SMB connections, which will expose this vulnerability. He advised users to check out the administrative page for the PCS, at Users -> Resource Policies -> Windows File Access Policiesto view current SMB policy.

A PCS policy that explicitly allows \\*or otherwise “may allow users to initiate connections to arbitrary SMB server names,” Dormann advised, telling users to “configure the PCS to Deny connections to such resources to minimize [...]

___________________________
@hacking_Attack
@Hacking_Video