Hacking Articles Tips Tricks Videos Tutorials
467 subscribers
65.6K 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: security in practice
How do i exploit this libSSH version?

Hello, so i'm currently doing a CTF, And when i ran a nmap scan i found the box was using libssh 0.8.4

so i looked it up and there seems to be a remote code execution vuln on that version, i guess that's the way to gain access.

I've seen a few tutorials on libSSH exploiting but i haven't seen anything about this particular CVE.

CVE-2019-14889.

I'm pretty sure the description of the vuln is pretty detailed and would give about anyone an idea on how to get inside the box, but i have just recently started pentesting and i'm kinda lost.

I don't know how the remote code could be executed, and what i should execute to gain access to the box.

Does anyone here have some useful advise?

submitted by /u/HackerArgento
[link] [comments]
Hi, hope you guys doing great! Here is a story about me finding a stored XSS using svg filesContinue reading on Medium » (https://prashantbhatkal2000.medium.com/svg-based-stored-xss-ee6e9b240dee?source=rss------bug_bounty-5)
CloudSpec - An Open Source Tool For Validating Your Resources In Your Cloud Providers Using A Logical Language
http://www.kitploit.com/2021/12/cloudspec-open-source-tool-for.html
CloudSpec is an open source tool for validating your resources in your cloud providers using a logical language that everybody can understand. With its reasonably simple syntax, you can validate the configuration of your cloud resources, avoiding mistakes that can lead to availability or confidentiality issues.
 IntroductionWith CloudSpec you validate resources in your cloud provider. A resource can be anything, from an EC2 Instance to an SES rule. Anything that a CloudSpec provider implements.Resources have properties and associations. Properties define the shape, or configuration, of the resource, while associations define its relationships with other resources. With CloudSpec, you not only can validate the configuration of the resource, but also the configuration of its associated resources. For example, let's take an EC2 Instance. It has properties defining its shape, like its unique instance ID, its name, its type, and the such. But it also has associations like the subnet (https://www.kitploit.com/search/label/Subnet) it belongs to, the EBS volumes attached to it, the AMI it uses, and the such. You not only can validate whether an EC2 Instance is of a particular instance type, or has the delete termination flag enabled, but also the size of its attached volumes, the CIDR block of its subnet, or any other property in its associated resources, or associated resources to its associated resources, and so on. You follow me.Your cloud resources are entangled together, creating a graph. A graph that you can traverse and validate as you see fit according to your best practices or compliance (https://www.kitploit.com/search/label/Compliance) policies. That ability, plus its logical language, is the beauty of CloudSpec.access logs enabled" on aws:s3:bucket assert access_logs is enabled end rule rule "Instances must use 'gp2' volumes and be at least 50GiBs large." on aws:ec2:instance with tags["environment"] equal to "production" assert devices ( > volume ( type equal to "gp2" and size gte 50 ) ) end ">set aws:regions = ["us-east-1", "eu-west-1"]

use "./my_module" as my_module

rule "Buckets must have access logs enabled"
on aws:s3:bucket
assert access_logs is enabled
end rule

rule "Instances must use 'gp2' volumes and be at least 50GiBs large."
on aws:ec2:instance
with tags["environment"] equal to "production"
assert devices (
> volume (
type equal to "gp2" and
size gte 50
)
)
end
You can find the full syntax in the CloudSpec Reference (https://cloudspec.pro/docs) documentation.ProvidersCloudSpec itself does not support any resource. The core of CloudSpec is the syntax interpreter for the specification files and its validation engine. However, CloudSpec does use providers, which are extensions to CloudSpec supporting each different type of resource.A provider defines the shape of each resource type, properties and associations, and the logic to load those resources.You can find the available providers and resources they provide in the CloudSpec Reference (https://cloudspec.pro/docs/)documentation.Running CloudSpec docker imageYou can either build and run the CloudSpec jar yourself, or you can run the latest docker image straight from the Docker Hub registry.To use the Docker image, you first need to put your spec files (e.g. specs/my_module) in a directory (https://www.kitploit.com/search/label/Directory) to mount it in the Docker container. Otherwise, the CloudSpec will not be able to open the spec files outside the container.export AWS_ACCESS_KEY_ID=***
export AWS_SECRET_ACCESS_KEY=***
export AWS_REGION=eu-west-1
docker run -v "/my_module:/my_module" -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_REGION efoncubierta/cloudspec run -d my_module
If you are running the docker container (https://www.kitploit.com/search/label/Container) in AWS with a dedicated IAM role attached, you can omit the AWS environment variables.For more options of the CloudSpec command, see help:docker run efoncubierta/cloudspec -h
Build CloudSpecIf you want to build CloudSpec yourself, follow these instructions.Requirements:GitMaven 3OpenJDK 8DockerPull the source code and build CloudSpec:# Clone git repo
git clone https://github.com/efoncubierta/cloudspec
cd cloudspec
# Build CloudSpec
mvn clean install
# Run CloudSpec
java -jar runner/target/cloudspec-${VERSION}.jar -h
CollaborationsFor the time being, this is a pet project and, therefore, only some resources in AWS are supported, but I am open to collaborations. Feel free to fork this project and send pull requests.

Download Cloudspec (https://github.com/efoncubierta/cloudspec)