GraphQL for Bug Bounty

GraphQL is getting popular day by day currently, it is being used by tech giants like Facebook, Twitter, Github and many more. In this…Continue reading on Developer Student Clubs SASTRA »
Read more...

Hacking on Medium
GraphQL explained

https://cdn-images-1.medium.com/max/2600/1*WjVr87nTkybfJLmZM8QFfg.png
Explanation of Graph QL in simple language.

Continue reading on Medium »

Hacking on Medium
GraphQL for Bug Bounty

https://cdn-images-1.medium.com/max/600/0*244CSegVtYKZGIul
GraphQL is getting popular day by day currently, it is being used by tech giants like Facebook, Twitter, Github and many more. In this…

Continue reading on Developer Student Clubs SASTRA »

GraphQL for Bug Bounty
https://medium.com/dsc-sastra-deemed-to-be-university/graphql-for-bug-bounty-48e669963d90?source=rss------bug_bounty-5

GraphQL is getting popular day by day currently, it is being used by tech giants like Facebook, Twitter, Github and many more. In this…Continue reading on Developer Student Clubs SASTRA » (https://medium.com/dsc-sastra-deemed-to-be-university/graphql-for-bug-bounty-48e669963d90?source=rss------bug_bounty-5)

SecretScanner - Find Secrets And Passwords In Container Images And File Systems
http://www.kitploit.com/2021/04/secretscanner-find-secrets-and.html

Deepfence SecretScanner can find any potential secrets in container (https://www.kitploit.com/search/label/Container) images or file systems.
What are Secrets?
Secrets are any kind of sensitive or private data which gives authorized users permission to access critical IT infrastructure (https://www.kitploit.com/search/label/Infrastructure) (such as accounts, devices, network, cloud based services), applications, storage, databases and other kinds of critical data for an organization. For example, passwords, AWS access IDs, AWS secret access keys, Google OAuth Key etc. are secrets. Secrets should be strictly kept private. However, sometimes attackers can easily access secrets due to flawed security policies or inadvertent mistakes by developers. Sometimes developers use default secrets or leave hard-coded secrets such as passwords, API keys, encryption (https://www.kitploit.com/search/label/Encryption) keys, SSH keys, tokens etc. in container images, especially during rapid development and deployment cycles in CI/CD pipeline. Also, sometimes users store passwords (https://www.kitploit.com/search/label/Passwords) in plain text. Leakage of secrets to unauthorized entities can put your organization and infrastructure at serious security risk. Deepfence SecretScanner helps users scan their container images or local directories on hosts and outputs a JSON file with details of all the secrets found. Check out our blog (https://medium.com/deepfence-cloud-native-security/detecting-secrets-to-reduce-attack-surface-3405ee6329b5) for more details.
Command line options
$ ./SecretScanner --help

Usage of ./SecretScanner:
-config-path string
Searches for config.yaml from given directory. If not set, tries to find it from SecretScanner binary's and current directory
-debug-level string
Debug levels are one of FATAL, ERROR, IMPORTANT, WARN, INFO, DEBUG. Only levels higher than the debug-level are displayed (default "ERROR")
-image-name string
Name of the image along with tag to scan for secrets
-json-filename string
Output json file name. If not set, it will automatically create a filename based on image or dir name
-local string
Specify local directory (absolute path) which to scan. Scans only given directory recursively.
-max-multi-match uint
Maximum number of matches of same pattern in one file. This is used only when multi-match option is enabled. (default 3)
-max-secrets uint
Maximum number of secrets to find in one container image or file system. (default 1000)
-maximum-file-size uint
Maximum file size to process in KB (default 256)
-multi-match
Output multiple matches of same pattern in one file. By default, only one match of a pattern is output for a file for better performance
-output-path string
Output directory where json file will be stored. If not set, it will output to current directory
-temp-directory string
Directory to process and store repositories/matches (default "/tmp")
-threads int
Number of concurrent threads (default number of logical CPUs)


Quickly Try Using Docker
Install docker and run SecretScanner on a container image using the following instructions: Build SecretScanner: docker build --rm=true --tag=deepfenceio/secretscanning:latest -f Dockerfile (https://www.kitploit.com/search/label/Dockerfile) . Or, pull the latest build from docker hub by doing: docker pull deepfenceio/secretscanning Pull a container image for scanning: docker pull node:8.11 Run SecretScanner: Scan a container image: docker run -it --rm --name=deepfence-secretscanner -v $(pwd):/home/deepfence/output -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker deepfenceio/secretscanning -image-name node:8.11

Scan a local directory: docker run -it --rm --name=deepfence-secretscanner -v $(pwd):/home/deepfence/output -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker deepfenceio/secretscanning -local /home/deepfence/src/SecretScanner/test
By default, SecretScanner will also create json files with details of all the secrets found in the current working directory. You can explicitly specify the output directory and json filename using the appropriate options.
Build Instructions
Install Docker Install Hyperscan Install go for your platform (version 1.14) Install go modules, if needed: gohs, yaml.v3 and color go get github.com/deepfence/SecretScanner will download and build SecretScanner automatically in $GOPATH/bin or $HOME/go/bin directory. Or, clone this repository and run go build -v -i to build the executable in the current directory. Edit config.yaml file as needed and run the secret scanner with the appropriate config file directory. For reference, the Install file (https://github.com/deepfence/SecretScanner/blob/master/Install.Ubuntu) has commands to build on an ubuntu system.
Instructions to Run on Local Host
./SecretScanner --help

./SecretScanner -config-path /path/to/config.yaml/dir -local test

./SecretScanner -config-path /path/to/config.yaml/dir -image-name node:8.11

Sample SecretScanner Output

Credits
We have built upon the configuration file from shhgit (https://github.com/eth0izzle/shhgit) project.
Disclaimer
This tool is not meant to be used for hacking. Please use it only for legitimate purposes like detecting secrets on the infrastructure you own, not on others' infrastructure. DEEPFENCE shall not be liable for loss of profit, loss of business, other financial loss, or any other loss or damage which may be caused, directly or indirectly, by the inadequacy of SecretScanner for any purpose or use thereof or by any defect or deficiency therein.

Download SecretScanner (https://github.com/deepfence/SecretScanner)

Black Hat Ethical Hacking
Legacy QNAP NAS Devices Vulnerable to Zero-Day Attack

https://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Legacy QNAP NAS Devices Vulnerable to Zero-Day AttackPost Views: 63
style="display:block"
data-ad-client="ca-pub-6620833063853657"
data-ad-slot="8337846400"
data-ad-format="auto"
data-full-width-responsive="true">
Reading Time: 1 Minute
Two critical zero-day bugs affect legacy QNAP Systems storage hardware, and expose devices to remote unauthenticated attackers.
The bugs, tracked as CVE-2020-2509 and CVE-2021-36195, impact QNAP’s model TS-231 network attached storage (NAS) hardware, allowing an attacker to manipulate stored data and hijack the device. The vulnerabilities, also impact some non-legacy QNAP NAS gear. However, it is important to note that patches are available for non-legacy QNAP NAS hardware.

A patch for the now-retired QNAP model TS-231 NAS device, first released in 2015, is scheduled to be released within weeks, QNAP representatives told Threatpost.

Patches for current model QNAP devices need to be downloaded from the QNAP download center and applied manually. Zero-Day DisclosureBoth bugs were disclosed on Wednesday by SAM Seamless Network researchers, who released limited technical details. The disclosure was ahead of official QNAP public disclosure of the vulnerabilities, and was in line with SAM Seamless Network’s disclosure policy of giving a vendor three months to disclose vulnerability details. Both flaws were found in the Oct. and Nov. 2020 timeframe and made public Wednesday.

“We reported both vulnerabilities to QNAP with a four-month grace period to fix them,” researchers wrote. “Due to the seriousness of the vulnerabilities, we decided not to disclose the full details yet, as we believe this could cause major harm to tens of thousands of QNAP devices exposed to the internet.”
See Also: Apple, Google Both Track Mobile Telemetry Data, Despite Users Opting Out
QNAP would not specifically say how many additional legacy NAS devices may be impacted. The company, in a statement to Threatpost said: “There are many hardware models of NAS in QNAP. (See: https://www.qnap.com/en/product/eol.php). In the list, you can find the models, the period of hardware repair or replacement, the supported OS and App updates and maintenance and the status of technical support and security updates. Most of the models, the security update could be upgraded to the latest version, i.e. QTS 4.5.2. However, some old hardware models have limits of firmware upgrade. For example, TS-EC1679U-SAS-RP could support only the legacy QTS 4.3.4.” Breaking Down QNAP Bug OneTracked as CVE-2020-2509, this remote code execution (RCE) bug is tied to firmware used in both old and new hardware, according to QNAP. Firmware versions prior to QTS 4.5.2.1566 (build 20210202) and QTS 4.5.1.1495 (build 20201123) are affected. Patches for current (non-legacy) hardware can be downloaded via QTS 4.5.2.1566 (ZIP) and QTS 4.5.1.1495 (ZIP).

The bug (CVE-2020-2509) resides in the NAS web server (default TCP port 8080), according to researchers.

“Previous RCE attacks on QNAP NAS models relied on web pages which do not require prior authentication, and run/trigger code in server-side. We’ve therefore inspected some CGI files (which implement such pages) and fuzzed a few of the more relevant ones,” researchers described.

They said that during the inspection, they were able to fuzz the web server with customized HTTP requests to different CGI pages, focusing on ones that didn’t require prior authentication. “We’ve been able to generate an interesting scenario, which triggers remote code execution indirectly (i.e[...]

., triggers some behavior in other processes),” researchers wrote.
See Also: Information Security Tool: Chameleon A fix for the vulnerability, suggested by researchers, is “adding input sanitizations to some core processes and library APIs, but it has not been fixed as of this writing.” Breaking Down QNAP Bug TwoThe second bug, tracked as CVE-2021-36195, is an unauthenticated RCE and arbitrary file-write flaw. It impacts QNAP TS-231’s latest firmware (version 4.3.6.1446), released in September.

The flaw allows two types of attacks. One allows a remote attacker – with access to the web server (default port 8080) – to execute arbitrary shell commands, without prior knowledge of the web credentials.

The second attack “allows a remote attacker with access to the DLNA server (default port 8200) to create arbitrary file data on any (non-existing) location, without any prior knowledge or credentials. It can also be elevated to execute arbitrary commands on the remote NAS as well,” according to researchers at SAM Seamless Network.

To exploit the bug, researchers created a proof-of-concept attack. “[We used] a python script that we wrote in order to hack into the device. We achieve full takeover of the device by using a simple reverse shell technique. After that, we access a file that’s stored on the QNAP storage. Any file stored can be accessed similarly.”

QNAP said a fix for supported hardware can be downloaded from the QNAP App Center and is identified as Multimedia Console 1.3.4. See Also: Hacking Stories: When two young hackers played war games with PentagonQNAP Patch Timeline“Currently, we have released the fix in the latest firmware and related app,” QNAP representatives told Threatpost. “Since the severity level is high, we would like to release the security update for legacy versions. It is expected to be available in a week. In addition, we hope there will be another week for users’ updates.”
Source: https://threatpost.com (Click Link)style="display:block"
data-ad-client="ca-pub-6620833063853657"
data-ad-slot="8337846400"
data-ad-format="auto"
data-full-width-responsive="true"> Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/04/iphone-privacy-90x90.jpg Apple, Google Both Track Mobile Telemetry Data, Despite Users Opting Out1 day ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Monero-Mining-90x90.png Malicious Docker Cryptomining Images Rack Up 20M Downloads2 days ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/phph-90x90.jpg PHP Infiltrated with Backdoor Malware3 days ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/ransomware_global_small-90x90.jpg Insurance Giant CNA Hit with Novel Ransomware Attack4 days ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Microsoft-Teams-90x90.jpg Microsoft Offers Up To $30K For Teams Bugs1 week ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/thrive-themes-1030x391-1-90x90.png Active Exploits Hit WordPress Sites Vulnerable to Thrive Themes Flaws1 week ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/HL-color-90x90.jpg Hobby Lobby Exposes Customer Data in Cloud Misconfiguration1 week ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/adobe_coldfusion-700x412-e1542041238507-90x90.jpg Adobe Fixes Critical ColdFusion Flaw in Emergency Update1 week ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/Clubhouse-e1614022265127-90x90.jpg Bogus Android Clubhouse App Drops Credential-Swiping Malware2 weeks ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/03/apple-security-90x90.jpg Trojanized Xcode Project Slips MacOS Malware to Apple Developers2 weeks ago
The post Legacy QNAP NAS Devices Vulnerable to Zero-Day Attack first[...]

appeared on Black Hat Ethical Hacking.

Deep Web
Please Help A Concerned Friend Out

My friend's pic got on this website without her permission. May I know the name of this website and what is it for?
https://d18fr4zq3fgp***************

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